Unless something is misbehavior, you generally need to use .bashrc, not
.bash_profile (this is bash's choice, not ours).
See the LAM FAQ, under "Booting LAM", the question "How do I add the LAM
executables to my $PATH?", as well as the bash man page; this topic is
discussed in detail.
On Sat, 3 May 2003, Jerome BENOIT wrote:
> 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' ?
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
