Re: rsh, rcp with bash

Article View: gnu.bash.bug

Article #236

#236

From: Mark Bush
Date: Thu, 30 Jul 1992 11:19

17 lines
1104 bytes

In article <2A7691FE.7354@tct.com> chip@tct.COM (Chip Salzenberg) writes:
#According to chet@po.cwru.edu:
#>Bash attempts to source the .bashrc for non-interactive shells running
#>rsh and rcp so things like $PATH get set.
#
#... which is, in my opinion, a BIG mistake.

Why is this a BIG mistake?  If this behaviour isn't the default and I want
it to happen, I have to mess with various things to get my .bashrc sourced.

If the .bashrc is known to be sourced, I can do things like checking PS1 to
see if I am interactive.

If I run `rsh host ls', then I want to know which `ls' I am running by
getting *my* PATH at the remote end.

Mark

Technical Details

Message-ID: <4176@inca.comlab.ox.ac.uk>

Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!prg.ox.ac.UK!Mark.Bush

References: <9207241236.AA02088.SM@odin.INS.CWRU.Edu>

Show Full Headers

Complete Article Headers

Newsgroups: gnu.bash.bug
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!prg.ox.ac.UK!Mark.Bush
From: Mark.Bush@prg.ox.ac.UK (Mark Bush)
Subject: Re: rsh, rcp with bash
Message-ID: <4176@inca.comlab.ox.ac.uk>
Sender: gnulists@ai.mit.edu
Organization: Oxford University Computing Laboratory
References: <9207241236.AA02088.SM@odin.INS.CWRU.Edu> 
Distribution: gnu
Date: Thu, 30 Jul 1992 11:19:31 GMT
Approved: bug-bash@prep.ai.mit.edu
Lines: 18

Reply to Parent Message