Forcing actions at login

[Mark Bush]

In article <1991Jan22.185016.15252 at freedom.msfc.nasa.gov> cornutt at freedom.msfc.nasa.gov (David Cornutt) writes:

> sets the HOME variable to it, and then sources the user's .login
> and .cshrc (if you want).  This way, the users can still have their 
> personalized logins if you want to let them do that, and you don't
> 
> Possible problems with this approach:
> [ problems (1) to (3) deleted ]

(4) The user may not necessarily have/want csh as their shell.  If a
    user wants the Bourne shell (for example) as their shell and your
    `global' account has the C-shell, then you can't just source their
    .profile.  Execing the user's real shell after setting HOME ought
    to work, though.

Another solution, of course, is to replace /bin/login with something
which does all the normal jobs and also checks for the existance of
some file to execute before starting up the user's shell.

Mark