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
> 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?
This is the reaason that SSH_SOURCE_BASHRC exists, but you have to
accept
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_
