Sam templates

[Terrence]

Sam templates and restricted Sam would seem to be the ideal way for me to allow a user to do all the account creation on a particular server. Unfortunately the create user template insists on appending the user name to the home directory setting. We use a generic home directory that is the same for every user. The application handles the data so I don't want several thousand home directories when one will do. I suppose worst case I could modify the /etc/skel/.profile and let sam create all those directories. But all the .profile needs to do is start the app. Maybe I'm being overly prissy, but it just seems inelegant. I want to make this easy for the user, so all they have to do is type in the user name and password, yet I don't want to give them any more access than absolutely necessary. Anyone know how to force Sam into behaving?

[Michael Tully]

Hi,

There is another option if you have
a script that generates the users/
passwords. You could set up sudo and
allow the user to run this task.

-Michael

[Terrence]

Sudo is definitely a possibilty, and I do have scripts doing this for other servers. This just seemed to be an easier cleaner way to have such a routine task performed with a minimal chance for screw ups.