> them. When I'm in slave02 or slave03 (by ssh), all lam
> execs are avaliable, but if I try 'rsh slave02 hboot'
> (exactly like lamboot does), 'hboot: command not
> found' is what I got, even if an command like 'rsh
> slave02 ls' is successfully.
>
try
rsh slave02 'which hboot'
and
rsh slave02 'echo $PATH'
to see if hboot is in your path on slave02
if it is not in your path, you need to modify your path on slave02 (remember to
do both .bashrc and .profile...)
When I suggested NFS, I meant, put LAM in your home directory some place, and
then NFS your home directory so that on every machine you have the same view.
-j
|
