Newsgroups: comp.parallel.pvm
Path: ukc!uknet!pipex!sunic!EU.net!Germany.EU.net!netmbx.de!zrz.TU-Berlin.DE!zib-berlin.de!uni-paderborn.de!urmel.informatik.rwth-aachen.de!newsserver.rrzn.uni-hannover.de!rz.uni-hildesheim.de!baghira.han.de!erni.escape.de!dagoba.escape.de!strauss
From: strauss@dagoba.escape.de (Frank Strauss)
Subject: Re: using printf/fprintf in debugging...
References: <peschko.758510138@s13>
Organization: Private Site
Date: Wed, 19 Jan 1994 18:13:47 GMT
Message-ID: <1994Jan19.181347.3337@dagoba.escape.de>
Lines: 18

peschko@arc.umn.edu (Ed Peschko) writes:

>I have written a master/slave program that is deadlocked somewhere -- in the
>slave process. Hence regular calls to fprintf(stderr, "...") don't work. 

Really? These prints should be dumped in the file /tmp/pvml.<uid> on the
first pvmd's host.

>Does anyone had a convenient way to print out slave process debugging
>info onto the console?

A simple method I often use, is to print this file using tail -f /tmp/pvml.422
for example.
-- 
"I made this letter longer than usual because I lack of time to make it shorter."
Frank Strauss        Email   (home) : strauss@dagoba.{escape|priconet}.de
Buergerstrasse 13             (uni) : strauss@{ips|ibr}.cs.tu-bs.de
38118 Braunschweig   /dev/audio     : (0531)-503873

