Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!apple!gem.mps.ohio-state.edu!wuarchive!cs.utexas.edu!uunet!mcsun!ukc!warwick!cudcv
From: cudcv@warwick.ac.uk (Rob McMahon)
Newsgroups: gnu.bash.bug
Subject: Re: bash seems to execute ".profile" when it shouldn't
Message-ID: <208@titania.warwick.ac.uk>
Date: 14 Sep 89 22:24:45 GMT
References: <8909130140.AA03372@wheat-chex>
Reply-To: cudcv@warwick.ac.uk (Rob McMahon)
Distribution: gnu
Organization: Computing Services, Warwick University, UK
Lines: 21

In article <8909130140.AA03372@wheat-chex> tmb@AI.MIT.EDU (Thomas M. Breuel) writes:
|	to quote from my locally hacked version of bash 1.03:
|	|   /* This is the only way I know how to find an rsh shell.
|	|      If this shell is remote (rsh host command), then make sure that
|	|      we run the .login stuff so that the user can set his/her PATH.
|
|If rsh wanted a login shell, it would invoke the shell with a "-" as 
|its first argument. For a variety of reasons, rsh doesn't. If that's the
|behavior someone wants for rsh, he should change the behavior of rsh, not of
|the shell.

This is vital.  It is quite normal for people to put things in .profile that
produce output.  Anything like this will blow rsh away (it will break the
protocol, since it is not expecting output).  Anything like PATH should be set
in the .bashrc.

Rob
-- 
UUCP:   ...!mcvax!ukc!warwick!cudcv	PHONE:  +44 203 523037
JANET:  cudcv@uk.ac.warwick             ARPA:   cudcv@warwick.ac.uk
Rob McMahon, Computing Services, Warwick University, Coventry CV4 7AL, England