Newsgroups: comp.parallel.pvm
From: nasng@comlab.ox.ac.uk (Shrinivas Gorur)
Subject: Re: pvmd3.3 can't be started on the remote machine
Organization: Oxford University Computing Laboratory
Date: Fri, 10 Jun 1994 09:08:42 GMT
Message-ID: <1994Jun10.090842.8262@pixie.comlab.ox.ac.uk>

> I am using PVM 3.3.0 since a couple of days. It works fine since my
> virtual machine is composed of one node (RS6K). I wanted to configure
> it with two nodes (2 RS6K) and got only one. Actually, the problem is that
> the demon pvmd3 can't be started on the remote machine. I just then looked
> into the PVM 3.3 manual to see if I had missed something. In fact, I didn't
> checked yet if the variable PVM_ROOT is set on the remote machine. It was not.
> 
> The cause of the problem is that my login SHELL is the ksh and not csh and
> with ksh, rsh command doesn't execute a configuration file like csh does
> with a .cshrc file. So all the problem is there. Since I will never go back
> to csh and love to use PVM with rsh, how could I make PVM sets PVM_ROOT on
> remote machines automatically ?

Actually you can easily overcome this by using a hostfile. The pvm console
can now do several things ...

a) you can start the pvm by a console with a hostfile

$ pvm hostfile


b) you can invoke a remote machine while setting its defaults thro the
console

pvm> add "newmachine dx=/newpath/pvmd"

c) If you have a uniform path on all the machines you use. Ex. if
/usr/people/loginid is the home provided thro a NFS on all the machines you
use then your hostfile needs to contain only one line

* dx=/usr/people/loginid/path_to_pvmdir/pvmdir/lib/pvmd

Actually pvm3.3 is really robust. All details for this present in 
a) Man pages
b) pvm3/doc/release-notes (which was posted by Bob Manchek to this news
group when he announced the availability of pvm3.3 on netlib)

regards
shrinivas


ps: There is nothing wrong with you shell. Infact ksh is _THE_ best. :-)

