Newsgroups: comp.parallel.pvm
Path: ukc!uknet!pipex!howland.reston.ans.net!sol.ctr.columbia.edu!news.kei.com!newsstand.cit.cornell.edu!cornell!uw-beaver!beaver!brad
From: brad@wormwood.cs.washington.edu (Bradford Chamberlain)
Subject: Q: task stdout/stderr
Message-ID: <BRAD.94Feb11170020@wormwood.cs.washington.edu>
Sender: news@beaver.cs.washington.edu (USENET News System)
Organization: /homes/gws/brad/.organization
Distribution: comp
Date: 11 Feb 94 17:00:20
Lines: 25


I just started using PVM yesterday, and so far have been having a great
time with few difficulties ramping up into it.  Got my first program
working within an hour or two of installing.

A question, however.  At the bottom of the C interface Refcard, I see
that stdout and stderr from all spawned tasks is redirected to
/tmp/pvml.<uid>.  This seems to agree with what I'm seeing.

What if I don't want this effect, however?  For example, if I'm using
PVM as an IPC mechanism on a single host and would like all output to
appear on the console?

Looking through the manual, I couldn't find any way to do this via the
PVM interface.  This seems to leave two choices:

1) UNIX-hack so that stdout and stderr are redirected to /dev/tty again.
2) send all output to the parent process which would then act as a
	uniform console for all tasks.

Have I missed something?  What paradigm do users use for terminal output?

Thanks!
-Brad


