Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!archimedes.math.uwm.edu!jgreco
From: jgreco@archimedes.math.uwm.edu (Joe Greco)
Newsgroups: comp.unix.wizards
Subject: Re: Automatic login script execution
Message-ID: <3385@uwm.edu>
Date: 11 Apr 90 19:10:42 GMT
References: <4147@uceng.UC.EDU> <780@barsoom.nhh.no> <40193@apple.Apple.COM>
Sender: news@uwm.edu
Organization: University of Wisconsin, Milwaukee
Lines: 18

In comp.unix.wizards article <40193@apple.Apple.COM>, vlb@Apple.COM (Vicki Brown) wrote:
: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?

Besides, there isn't a heck of a lot that you can do in a cshrc that cannot
be undone on the command line.

Generally users do not seem to change things in their .cshrc files that they
do not understand.  This applies to about 90% of the users on this site.
Anybody knowledgeable enough to want to change whatever it is that you want
to put in it probably knows why you did it and why they should want to do
otherwise.

... Joe