Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!caen!news
From: stealth@caen.engin.umich.edu (Mike Pelletier)
Newsgroups: comp.mail.uucp
Subject: HDB UUCP question -- how to avoid spurious error messages?
Message-ID: <1990Sep30.230132.7664@caen.engin.umich.edu>
Date: 30 Sep 90 23:01:32 GMT
Sender: news@caen.engin.umich.edu (CAEN Netnews)
Organization: caen
Lines: 25

I have a TCP UUCP link to a system that calls me but does not allow me
to call it -- it's using SLIP over a 2400 baud modem, thus it likes to be
in charge of when and how the narrow bandwidth is used.
Because of this, I have "b-tech Never" for its entry in my Systems
file.  However, the UUCP software still attempts a connection,
since I commonly get error messages like:

uucp b-tech  (9/30-16:41:05,1614,0) CONN FAILED (WRONG TIME TO CALL)
uucp b-tech  (9/30-17:11:04,2712,0) CONN FAILED (WRONG TIME TO CALL)
uucp b-tech  (9/30-17:41:04,3781,0) CONN FAILED (WRONG TIME TO CALL)
uucp b-tech  (9/30-18:11:04,5201,0) CONN FAILED (WRONG TIME TO CALL)

The times on these correspond to the time that "uusched" is run from
crontab.
Any idea how I can make uusched pay attention to the fact that it
shouldn't even be attempting to call b-tech?
Thanks!


--
	Mike Pelletier - Usenet News Admin & Programmer
                             --
"Wind, waves, etc. are breakdowns in the face of the commitment to getting
 from here to there.  But they are the conditions for sailing -- not
 something to be gotten rid of, but something to be danced with."