Re: Is this expected ssh behavior?
Brandon Mitchell <email@example.com> writes:
> I'm kind of curious why bash is not running your .bash files.
As am I. It runs them just fine if I just do "ssh somehost". But if
I do "ssh somehost bash -c umask", I can tell that it hasn't run my
startup scripts. Further "ssh somehost bash" doesn't even give a
prompt. Ahh, now the pieces begin to fall into place...
I just noticed that "ssh somehost bash -i" *does* give me a prompt,
and that "ssh somehost bash -i -c umask" indicates that the scripts
are being run. However, the $PATH I get with "ssh somehost bash -i"
indicates that although it's sourcing my ~/.bash* scripts, it's not
So it looks like ssh on a Debian system's running bash with something
like "--noprofile", and the -i doesn't get /etc/profile, just your ~
scripts. If that's what's happening, is that what we want?
Rob Browning <firstname.lastname@example.org> PGP=E80E0D04F521A094 532B97F5D64E3930
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org