Forcing actions at login

[Sh'r'ldana]

In article <6153 at ecs.soton.ac.uk> tjc at ecs.soton.ac.uk (Tim Chown) writes:
>I would like to know the neatest way of forcing certain actions to
>be taken when a user logs in to the system.  For example, I would
>like to ensure everyone sees the global message of the day, or 
>perhaps get reniced if they're not a priority user on machine X.
>
>Is the recommended way to simply put the name of a script in the
>passwd file instead of /bin/csh (or whatever)?  I can't see any
>other alternative as the user has to own .login, but are there
>any ill side-effects from this action?
>
>Tim

The system that has been implemented here was to write a shellscript to run 
the commands, and put it in place of the default login-shell field.  Ours is
only to allow the user to log in and change the password from the default we
give them to something they want, and then log out, but it should be expandable,
possible with 'exec {whatevershell}'.

Steve

--
anagram at desire.wright.edu | "Tough times demand tough hearts, demand tough 
spotter at eve.wright.edu    |  thoughts, demand tough songs, 
			  |  Demand!" -Rush
<Std.Dsc> WSU doesn't approve of anything I do, but that hasn't stopped me yet.