🚀 go-pugleaf

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.
|
| Thus the following patch to Bash 1.12 to eliminate that behavior:

How come?  I've been holding up bash as the state of the art in getting
that one right.  Shells like the Korn shell that never run a startup script
unless they're login shells leave people scratching their heads over things
like

	$ rsh there xterm -display $DISPLAY
	ksh: xterm: not found

(There are workarounds, if you want to try "/bin/login.ksh" or "/bin/-ksh" as
your login shell.)  Shells like csh that always run a startup script are even
worse, and there's no workaround for that.  That's where bash occasionally
gets into trouble - bash -c will run .bashrc if its environment hasn't been
prepared by another bash process.

The stock answer to all this in some quarters is "fix rshd".  I'd be happy
to have rshd start a login shell, but then I'm pretty comfortable with the
idea of organizing my .profile with a lot of shell logic; lots of users
would have trouble with that.

	Donn Cave, University Computing Services, University of Washington
	donn@cac.washington.edu