Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site sjuvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!astrovax!sjuvax!bbanerje
From: bbanerje@sjuvax.UUCP (B. Banerjee)
Newsgroups: net.bugs.uucp,net.unix-wizards
Subject: Re: does FPE toggle Debug level?
Message-ID: <459@sjuvax.UUCP>
Date: Thu, 16-Aug-84 00:38:21 EDT
Article-I.D.: sjuvax.459
Posted: Thu Aug 16 00:38:21 1984
Date-Received: Fri, 17-Aug-84 01:04:12 EDT
References: gargoyle.180 <1172@rti-sel.UUCP>
Organization: Saint Josephs Univ. Phila., Pa.
Lines: 28

>> To see if uucico is hung,
>> (a) if it is recieving a file see if a TM. file is growing.
>> (b) if it is sending a file, estimate the time needed and see if uucico
>> 	has taken too long.
>> Also, an 'iostat 5' might help indicate uucico tty traffic.
>> 	Tom Truscott

The kludgy way I handled this on our (4.2) uucp was to redefine
DEBUG in uucp.h.  I just changed it to

#define DEBUG(l,f,s) if (Debug >= 1) fprintf(stderr, f, s); else \
	debugentry(1, f, s) <-- That first argument is a one.

debugentry was a routine I wrote that appended the stuff onto
a file called DEBUG in the uucp spool directory.  I then do a
"tail -f" of DEBUG whenever I want to monitor the progress of an
ongoing uucp transaction.  It can get slightly hairy when there
are more than one uucp transactions going simultaneously, but I
haven't had any real problems so far.

It isn't pretty, but it works.

Regards,
-- 
				Binayak Banerjee
		{allegra | astrovax | bpa | burdvax}!sjuvax!bbanerje
P.S.
	Send Flames, I love mail.