Xref: utzoo comp.sys.ncr:182 comp.mail.uucp:4058
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.sys.ncr,comp.mail.uucp
Subject: Re: More on Polling and uusched
Message-ID: <3017@auspex.auspex.com>
Date: 10 Mar 90 23:32:06 GMT
References: <2037@sauron.Columbia.NCR.COM> <3000@auspex.auspex.com> <2045@sauron.Columbia.NCR.COM>
Followup-To: comp.mail.uucp
Organization: Auspex Systems, Santa Clara
Lines: 27

(Not really NCR-specific, so I'm forwarding this to "comp.mail.uucp".)

 >> > >[Discussion of why, when you put "Never" as the time to call in the
 >> > >"L.sys"/"Systems" file, it insists on logging "WRONG TIME TO
 >> > >CALL" messages every time you try to call, when there isn't any
 >> > >*right* time to call]
 >> > You don't really want it to fail silently, regardless of the reason.
 >
 >> Uh, yes, I do; that's why, at one place, I modified "uucico" to
 >> specifically know about "Never" (or maybe I called it "Slave" or
 >> something) and not bother to let me know something I already *did* know,
 >
 >I'd argue that it's the cases where you don't know and are trying to
 >debug that you want definite reasons for failure to call.

If you don't know, the first step in debugging would seem to *me* to be
to, well, read "L.sys" or "Systems", after which you *would* know. 
What's more, I'd expect that most of the time you *wouldn't* be
debugging things, so...

 >One could disble "Wrong time to call" logging if "Never" is found and
 >if debug == 0.

...is a reasonable idea - in fact, I might suggest disabling "Wrong time
to call" messages if debug == 0, period (what about a machine to which
people send mail and/or news at all times of the day, but which is only
called after 11PM?).