Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!tolerant.UUCP!uucp
From: uucp@tolerant.UUCP (UNIX-UNIX Cp)
Newsgroups: comp.unix.microport
Subject: Submission for comp-unix-microport
Message-ID: <8901061437.AA25405@handel.TOLERANT>
Date: 6 Jan 89 14:36:58 GMT
Sender: uuclerk@ucbvax.BERKELEY.EDU
Lines: 25

Path: tolerant!voder!pyramid!amdahl!ames!haven!aplcen!wb3ffv!fallst!tkevans
From: tkevans@fallst.UUCP (Tim Evans)
Newsgroups: comp.unix.microport
Subject: uPort 2.4 'cron' and/or HDB 'Poll'
Message-ID: <491@fallst.UUCP>
Date: 2 Jan 89 14:25:20 GMT
Organization: Tim Evans, Fallston, MD
Lines: 16

I'm finding that uPort 2.4 seems to have corrected the old 'cron' bug
(i.e., everything ran twice), _except_ with respect to UUCP calls 
generated by the HDB 'uudemon.poll'.  These still seem to get generated
in twos.  (I run this script via cron every half hour, then run
'uusched' a little later--also every half hour.)  Whenever 
'uudemon.poll' generates its "phony" work file for a system, it seems
to do so in such a way that the remote system gets called _twice_,
a half hour apart.

Anyone know anything about this?

-- 
UUCP:  ...!{rutgers|ames|uunet}!mimsy!aplcen!wb3ffv!fallst!tkevans
INTERNET:  tkevans%fallst@wb3ffv.ampr.org
OTHER: ...!attmail!fallst!tkevans
Tim Evans  2201 Brookhaven Court, Fallston, MD  21047   (301) 965-3286