Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!raybed2!rayssd!galaxia!dave
From: dave@galaxia.Newport.RI.US (David H. Brierley)
Newsgroups: comp.unix.admin
Subject: Re: Forcing actions at login
Message-ID: <1135@galaxia.Newport.RI.US>
Date: 18 Jan 91 01:48:50 GMT
References: <1991Jan10.191546.268@am.sublink.org> <449@minya.UUCP> <1991Jan16.000012.26467@lokkur.dexter.mi.us>
Organization: Dave's Very Own Personal System
Lines: 16

I took a slightly different approach to this problem.  I modified the login
program so that when it got done validating the password and doing whatever
else it wanted, instead of execing the users shell it execed a program that
I had written called 'sh_init'.  The sh_init program then took care of all
of the global stuff that needed to be done including displaying the motd
file, setting a bunch of variables in the environment, and asking the user
what 'charge number' they would be using for this session.  The program
also has hooks for running a machine-specific init file.

Admittedly, this approach requires that you have source to the login program
but there are enough PD login programs floating around that this should not
be a real problem.
-- 
David H. Brierley
Home: dave@galaxia.Newport.RI.US    Work: dhb@quahog.ssd.ray.com
Can I be excused, my brain is full.