scp not tolerant of extraneous shell messages

[Bob Proulx]

> If Bash actually followed its own principles, scp would not have a
> problem, because Bash would not run .bashrc.  It is only because the
> rshd hack (wherein Bash apparently mistakes the scp session for an
> interactive rsh session) makes Bash invoke .bashrc in a shell that is
> not interactive that scp has a problem with conversational messages
> from .bashrc.

The root of the problem is that rshd uses a compiled in PATH which
rarely contains what the user needs.  (The same for ssh.  But that has
been discussed at length and future development outlined.)  Therefore
as a workaround bash loads a .bashrc which can set up PATH and other
variables so that the rsh will actually work.  I don't like it
either.  But it does add functionality which would otherwise be
missing.

Even typing in a hard coded path to a program (/usr/local/bin/foo)
won't work if that program in turn calls another program from the same
location (/usr/local/bin/bar).  It is all hacks upon hacks.

Bob