CVS log for loncom/Attic/lchtmldir

Up to [LON-CAPA] / loncom

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN
Current tag: MAIN

- Web interface to support switching/adding filesystem-authenticated
  "unix" users was removed in LON-CAPA 2.6.0, so lcuseradd not needed.
- Authoring Spaces migration from /home/<username>/public_html to
  /home/httpd/html/priv/<domain>/<username> for 2.11.0, so lchtmldir
  not needed (bug 1320).

Get this to run on FC13 - problem is that once one drops euid to actual uid
you evidently can't
raise it again..so rather than dropping priv to check actual uid just
ask for the actual uid directly without setting the euid to the actual uid.

Bug 5721.
Debug message should show the correct format for the expected arg.

- add in revision info

- switch to using $match_username

Allow users with usernames including . and - to have public_html directories, when given an author role.

For internally authenticated users, the top level
dir needs to have a+x in order to allow www to enter
~/public_html - see defect 4118

- commiting Martin Siegert's updates to work on systems that don't create user groups by default

Fix some safing issues with the pid for httpd that prevented the
kill -USR1 from being sent to the right pid.

Ensure that lond invokes lchtmldir for authors that switch both in and
out of filesystem auth mode.

Reset the ownership to user:user rather than user:www even though the latter
is objectively probably better and I don't think it will break any existing
stuff since the www already has groups for users that don't match this scheme.

Fix defect 3853: Directory ownerships were not correct if the user
was to become an author e.g.  Set the ownerships as follows:
top level dir: username:www  public_html and below username:www
everything else, the user should be able to control via their Unix
login and should be, if deisired, hide-able from LonCAPA.

For internal users, fork off the creation of the restore file
and permission settings to try to avoid lond timeouts.

When the auth mode is being changed to internal, and the user has a
/home/username dir (has authorship role), prior to setting the permissions
and ownership, write a script named restore_n.sh in the users's /home/username
diretory that will restore all currently extant files to their prior ownershp
and permissions.  This is done in case a filesystem user is accidently changed
into an internal user and then is changed back... the default action of
lchtmldir in that case may leave files without the prior permissions, if the
user did some interesting stuff with group ownership, or had sensitive stuff.

The user can the login, locate the most recent version of the script and
execute it to get back to something close to what they had before

Latent support for saving full directory tree permission/ownerships
in the form of a script that can be run to restore.  This would be used
when changing a file system authenticated user to internally authenticated
in order to support rolling their directory ownership/permissions back.

DEFECT 550: Reset ownership of top level user directory if internal.
     This is required for Fs -> internal auth changes of authors.

- actualy parse the result of the groups command correctly

- remove -w mode and some Debug spew

i- part of BUG#3238, lchtmldir was incorretly using tainted data,

More correct first file in construction space.

Allow creation of public_html directories for users who are not filesystem
authenticated.  Implement changing ownership of directories to www:www for
kerberos and local authentication as well as internal authentication.

Forgot to propagate change for -p switch into mkdir.

Fixes for BUG 259:
  lhctmldir - New script to created author construction space directories
for users.
  lond - Centralized auth mode info in a sub.
         call lchtmldir as appropriate when a user gains authorhip access.

setuid script to do what's necessary with a user's ~/public_html
directory when they are given author role.  If necessary, this directory
will be created, regardless, proper ownership/permissions will be set and
if necessary an initial index.html file will be created.