https://bugzilla.novell.com/show_bug.cgi?id=345570
User vincent@vinc17.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=345570#c2
--- Comment #2 from Vincent Lefevre 2007-12-04 05:36:34 MST ---
Indeed the upstream http://tiswww.case.edu/php/chet/bash/CHANGES file says:
[...]
This document details the changes between this version, bash-2.05a-rc1,
and the previous version, bash-2.05a-beta1.
[...]
z. Bash no longer attempts to discover if it's being run by sshd in order to
run the startup files. If the SSH_SOURCE_BASHRC is uncommented in
config-top.h it will attempt to do so as previously, but that's commented
out in the distributed version.
This is also mentioned in http://tiswww.case.edu/php/chet/bash/COMPAT (change
17).
and Debian's README.Debian.gz file contains:
- try to check whether bash is being run by sshd and source
the .bashrc if so (like the rshd behavior).
Now, the bash man page doesn't reflect the upstream behavior (sshd is the
remote shell daemon nowadays). And this doesn't explain why there's a visible
difference between "ssh <host> <cmd>" and "ssh -t <host> <cmd>", concerning
this point.
I've just sent a mail to bug-bash about this point.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.