I think the fact that ~/.bash_profile is not executed is due to the
fact that bash distinguishes between interactive-shell,where you have a
command-prompt, and non-interactive-shell,
which regards only a subset of your dot-files.
When you call 'ssh remote-host command', the non-interactice-shell is
used, and your ./bash_profile is skipped. One way to get it working is
to add your PATH to your ./bashrc, the other is to add the PATH-variable
to ~/.ssh/environment( see man ssh)
good luck
Andre
Jerome BENOIT wrote:
> Hello LAM,
>
> I am working on a small network with `bash' as shell and `ssh' as rsh:
> I wonder why `lamboot' does not source the ~/.bash_profile'
> (in order to have a correct PATH before to look for `lamd')
> as `ssh' does set a default PATH then:
> whereas once ssh connected to XX `printenv PATH' gives the PATH as set
> up in `~/.bash_profile',
> ssh XX "printenv PATH" gives the default PATH
> (in other words, the `~/.bash_profile' was not sourced).
>
> I do not know who misbehaves.
>
> Anyhow,
> can we ask to `lamboot' source `~/.bash_profile' before to look for
> `lamd' ?
|
