If you can, make the target of your ssh invocation a wrapper script that sources .bashrc and then executes the remaining arguments.
Something like (in /usr/bin/local/ssh-target.sh): #!/usr/bin/env bash .[ -f ~/.bashrc ] && . ~/.bashrc "$@" ssh [EMAIL PROTECTED] /usr/local/bin/ssh-target.sh cmd args... At the cost of having to have /usr/local/bin/ssh-target.sh (or equivalent) available everywhere, you can at least avoid dependencies on particular combinations of ssh and bash. jon. On Thu, Oct 23, 2008 at 9:52 PM, Roman Rakus <[EMAIL PROTECTED]> wrote: > Roman Rakus wrote: >> >> and with this change .bashrc is never sourced. Will we do something with >> this? Changing check from socket to pipe stdin will cause problems with >> older ssh. Maybe defining SSH_SOURCE_BASHRC? Or just don't do anything? >> RR >> >> > This is invoked by > https://bugzilla.redhat.com/show_bug.cgi?id=458839 > RR > > >
