Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!vlb
From: vlb@Apple.COM (Vicki Brown)
Newsgroups: comp.unix.wizards
Subject: Re: Automatic login script execution
Message-ID: <40193@apple.Apple.COM>
Date: 10 Apr 90 23:40:22 GMT
References: <4147@uceng.UC.EDU> <780@barsoom.nhh.no>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 27

In article <780@barsoom.nhh.no> tholo@barsoom.nhh.no (Thorsten Lockert) writes:
>schriste@uceng.UC.EDU (Steven V. Christensen) writes:
>>Can anyone point me to a login.c replacement which causes a global
>>.login file to be executed first? I assume I would place a "source ~/.login"
>>as the last line of this global file.
>
>Um, wont't /etc/profile and/or /etc/cshrc do that right now?

Unfortunately, /etc/cshrc is not standard (it is not in BSD 4.3 and it does not
appear to be in SunOS 4.0).  On A/UX, the sources indicate that /etc/cshrc
is derived originally from UniSoft.  It would also appear that /etc/profile
is not standard either.

My personal inclination is to lean towards using a standard .login/.profile
somewhere, setting up new users accounts to source this file, and including
comments to tell them why they want to.  (I've never liked sysadmins who force
me to do something.)  What, precisely, are you doing for these people that
you must force it to be done?  Can't you explain why they don't want to edit
things away?

If you are only looking for notification (rather than variable setting
and the like), why not /etc/motd?
-- 
Vicki Brown			(408) 974-2120
A/UX Engineering		vlb@apple.com

all opinions are mine (but I'm willing to share :-)