I have done sys admin on Crays, Convexes, Suns, SGIs,
Decs, PC running BSDI, Linux and Free BSD, and I have
never run into a system where the .cshrc is sourced
AFTER the .login.
If someone goes to the trouble to change the order,
I would love to know a valid reason for it.
Lyle
From guenther(_at_)gac(_dot_)edu Mon Aug 17 23:56:22 1998
To: lyle(_at_)infi(_dot_)net
Cc: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Subject: Re: tcsh
From: Philip Guenther <guenther(_at_)gac(_dot_)edu>
lyle(_at_)infi(_dot_)net (Lyle D. Sanders) writes:
Actually, csh and tcsh, executes the .cshrc first, THEN if, and only
if it is the login shell (not a sub shell) it executes the .login.
While I have never used such a system, I have been told by other
sysadmins that there are systems on which csh was hacked to source
the .login before the .cshrc. For various reasons I suspect these
to be systems based on older versions of BSD (say, 2.3 BSD).
As for tcsh, the order in which the .login and .cshrc is sourced is a
compile time option which defaults to the .cshrc (or .tcshrc) before
the .login. There may be some wackos out there who change the default
in memory of the system(s) that they were raised on. I suggest
electroshock as the proper treatment.
Philip Guenther