Newsgroups: comp.parallel.pvm
From: wrankin@ee.duke.edu (William T. Rankin)
Subject: Re: pvmd3.3 can't be started on the remote machine
Organization: Duke University EE Dept.; Durham, NC
Date: 9 Jun 1994 22:35:00 GMT
Message-ID: <2t85ek$2i6@news.duke.edu>

In article <2t7p7b$i12@upsn2.u-psud.fr>, chergui@idris.fr (Jalel Chergui) writes:

|>      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 ?

well, i too am a ksh user, having gotten addicted during a five year
stint with AT&T.  you have a couple options:

   1) start pvm with a hostfile and make the first line
      of the hostfile:

           * dx=/usr/local/pvm3

      or where ever you store pvm.

   2) does ksh exec $HOME/.kshrc when being called remotely?
      if yours does then you can put the following in your 
      .kshrc file:

           PVM_ROOT=/usr/local/pvm3 ; export PVM_ROOT

      type the command

           rsh <machine> 'echo $PVM_ROOT'

      to see if it works

   3) finally, the brut force method is to specify the pvmd location
      on the command line from within pvm.  try typing:

           add "<machine> dx=/usr/local/pvm3"


Hope this helps.

-bill


-- 
----                                /       __/    /    /
bill rankin                        /              /    /
wrankin@ee.duke.edu               ___  /    /    /    /
graduate weenie                  /    /    /    /    /
                                /    /    /    /    /
                             _______/  __/  __/  __/



