Newsgroups: comp.parallel.pvm From: Robert Saulnier Subject: Re: Problem with win32 pvm console Organization: University of New Brunswick Date: Wed, 24 Jun 1998 09:56:31 -0300 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------D6714B576672AD2C801B94E7" Message-ID: <3590F77F.95318752@nbnet.nb.ca> --------------D6714B576672AD2C801B94E7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kevin Parker wrote: > I am an experienced pvm user on unix & thought I would try the win32 > (pvm3.4beta6) version on win95. When I launch pvm console I get the > following messages and the console quits. > > "libpvm [pid-xxxxxx] mksocks() connect: No such file or directory" > "libpvm [pid-xxxxxx] mksocks() connect: Bad file descriptor" > "libpvm [pid-xxxxxx] Console: Can't contact local daemon" > > the pvmd is running, and the log files (/tmp/pvml.x /tmp/pvmd.x) do not > indicate a problem. I am using ataman rshd. > > any help would be appreciated > kevin What you need to do is delete the file pvmd. from the temp directory. Then try running your console again. This should fix things. When you run a daemon on a PC it creates the file mentioned, but if the daemon is terminated before it can delete this file, you won't be able to start a new one till you delete it. Robert --------------D6714B576672AD2C801B94E7 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

Kevin Parker wrote:

I am an experienced pvm user on unix & thought I would try the win32
(pvm3.4beta6) version on win95. When I launch pvm console I get the
following messages and the console quits.

"libpvm [pid-xxxxxx] mksocks() connect: No such file or directory"
"libpvm [pid-xxxxxx] mksocks() connect: Bad file descriptor"
"libpvm [pid-xxxxxx] Console: Can't contact local daemon"

the pvmd is running, and the log files (/tmp/pvml.x /tmp/pvmd.x) do not
indicate a problem. I am using ataman rshd.

any help would be appreciated
kevin

  What you need to do is delete the file pvmd.<userid> from the temp directory. Then try running your console again. This should fix things.
When you run a daemon on a PC it creates the file mentioned, but if the daemon is terminated before it can delete this file, you won't be able to start a new one till you delete it.

Robert --------------D6714B576672AD2C801B94E7--