Path: utzoo!attcan!uunet!mcsun!ukc!ox-prg!culhua!bush
From: bush@prg.ox.ac.uk (Mark Bush)
Newsgroups: comp.unix.admin
Subject: Re: Forcing actions at login
Message-ID: <BUSH.91Jan23103945@sapphire.prg.ox.ac.uk>
Date: 23 Jan 91 10:39:45 GMT
References: <6153@ecs.soton.ac.uk> <446@minya.UUCP>
	<1991Jan10.191546.268@am.sublink.org> <449@minya.UUCP>
	<1991Jan16.000012.26467@lokkur.dexter.mi.us>
	<1991Jan22.023543.934@melb.bull.oz.au>
	<1991Jan22.185016.15252@freedom.msfc.nasa.gov>
Sender: news@prg.ox.ac.uk
Organization: Oxford University Computing Laboratory, UK
Lines: 20
In-reply-to: cornutt@freedom.msfc.nasa.gov's message of 22 Jan 91 18:50:16 GMT

In article <1991Jan22.185016.15252@freedom.msfc.nasa.gov> cornutt@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