Path: utzoo!mnetor!uunet!tektronix!reed!tessi!joey
From: joey@tessi.UUCP (Joe Pruett)
Newsgroups: comp.unix.questions
Subject: Re: 4bsd .login and .cshrc
Message-ID: <453@q7.tessi.UUCP>
Date: 29 Mar 88 19:11:20 GMT
References: <326@ivory.SanDiego.NCR.COM> <7765@apple.Apple.Com> <27717@linus.UUCP> <111@infmx.UUCP> <27@denali.UUCP> <3126@csli.STANFORD.EDU>
Organization: TSSI, Beaverton, Oregon
Lines: 24

As has been mentioned, rsh does not source your .login file.  This is
quite obnoxious when you set your path in your .login (where it belongs
so that each shell isn't hashing your path more than necessary).
"rsh hostname something_in_usr_local_bin" will get you a "Command not
found" message.  To get around this problem I've renamed .login to
.mylogin and created a new environ variable that let's my .cshrc know
if my .mylogin has been run, if not then .cshrc sources .mylogin.

In .cshrc:
if ( ! ${?MYLOGIN} ) source ~/.mylogin
.
.

In .mylogin:
set path = ( . . . )
.
.
setenv MYLOGIN ""

This could be cleaned up a little bit (move the env stuff into
.cshrc inside the if MYLOGIN line), but inertia can be quite
overwhelming.
--
Joe Pruett        ...!tektronix!tessi!joey