https://bugzilla.novell.com/show_bug.cgi?id=244788 suse@tlinx.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #10 from suse@tlinx.org 2007-03-09 17:31 MST ------- Sorry to take time to test this -- I "virtually" always have too much on plate, so timeslicing takes a bit -- (keep waiting for brain-hardware update, but ...) The above doesn't fix my problem but could with a minor "tweak". specifically, in /etc/profile, the conditional for being in SSH needs to be around not just the call the "/etc/bash.bashrc", but also around the _user's_ ".bashrc" (and likely need the logic to encompass the following calls to the ksh equivalents. I.e. looks like you added "+" replacing "-" lines; other lines included for context # System BASH specials, maybe also good for other shells # Note that ksh always reads /etc/ksh.kshrc # + if test "$is" != ksh -a -z "$_SOURCED_FOR_SSH" ; then + test -r /etc/bash.bashrc && . /etc/bash.bashrc + fi # (replacing) - if test "$is" != ksh -a -r /etc/bash.bashrc ; then - . /etc/bash.bashrc - fi if test "$is" = "bash" -a -z "$_HOMEBASHRC" ; then # loop detection readonly _HOMEBASHRC=true test -r $HOME/.bashrc && . $HOME/.bashrc .. ----------- But, you need to have your above logic also blocking a redundant call to the users ".bashrc", and you need to also make sure that the same checks are done for the ksh users -- so something like this: if -z "$_SOURCED_FOR_SSH"; then # # System BASH specials, maybe also good for other shells # Note that ksh always reads /etc/ksh.kshrc # if test "$is" != ksh ; then test -r /etc/bash.bashrc && . /etc/bash.bashrc if test "$is" = "bash" -a -z "$_HOMEBASHRC" ; then # loop detection readonly _HOMEBASHRC=true test -r $HOME/.bashrc && . $HOME/.bashrc fi fi -------- I put "SOURCED_FOR_SSH" as a separate test and was going to have the ".kshrc" code also not called when sourced from SSH -- seems like it would make parallel sense, but the ksh logic is different from the bash logic, so the same fix might not work for ksh. -l -- 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, or are watching someone who is.