[SSH]Which login scripts are run?

jamesstanley · 11-17-2007, 04:27 AM

Long Description
I am trying to set up an MPICH2 beowulf cluster, just for fun.
I have got mpd to run processes on localhost, and I have setup passwordless SSH login.
My problem is that when mpdboot tries to execute mpd's on the other host (only one other until I can get it working

), it fails because /usr/mpich/bin is not in the path.

Short Description
Which login scripts are run when SSH logs in, without bash being executed? I know some must be because...

Code:

ssh 192.168.1.102 'echo $PATH'

has an output.

unSpawn · 11-17-2007, 05:23 AM

Quote:

Originally Posted by jamesstanley

Which login scripts are run when SSH logs in, without bash being executed?

An elaborate way would be to add echoes to your global and the accounts resource scripts and you'll see soon enough what gets sourced. A less elaborate way would be to 'man ssh', check under "Login session and remote execution". And what do you mean "without BASH being executed"? Did you doctor the account so it has no shell or what?

Quote:

Originally Posted by jamesstanley

My problem is that when mpdboot tries to execute mpd's on the other host (only one other until I can get it working

), it fails because /usr/mpich/bin is not in the path.

Can't you just use the full path if you don't want to add /usr/mpich to your PATH?

lakris · 11-17-2007, 05:37 AM

When You do

Quote:

$ ssh 192.168.1.102 'echo $PATH'

you will have "broadly speaking" the environment of the calling user.

When You do

Quote:

$ ssh 192.168.1.102
$ echo $PATH

you will have the environment of the remote user.

I am not all together certain to what extent a ssh-session read profile, .bashrc etc when logging in but You can set some of it in /etc/ssh/ssh_config (or something similar). Ssh also set a few environment variables by default but You can specify more of 'em in ~/.ssh/environment.

/L

jamesstanley · 11-17-2007, 06:24 AM

Quote:

An elaborate way would be to add echoes to your global and the accounts resource scripts and you'll see soon enough what gets sourced

I tried that in:
~/.bashrc
~/.bash_profile
~/.bash_login
~/.profile
/etc/bashrc
/etc/profile

Nothing got echoed.

Quote:

you will have "broadly speaking" the environment of the calling user.

I had /usr/mpich/bin in the path of the calling user, but not the SSH session (same user, same host).

Quote:

Can't you just use the full path if you don't want to add /usr/mpich to your PATH?

It's not hat I want it in the path, it's that mpich won't work without it in the path. I suppose I could edit the mpdboot script, but it would be nicer to do it the right way.

I'm going to check the man page now.

EDIT:
Ah.
~/.ssh/rc is the file I want.