stealth@caen.engin.umich.edu (Mike Pelletier) (10/01/90)
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."jmaynard@thesis1.hsch.utexas.edu (Jay Maynard) (10/01/90)
In article <1990Sep30.230132.7664@caen.engin.umich.edu> stealth@caen.engin.umich.edu (Mike Pelletier) writes: >Any idea how I can make uusched pay attention to the fact that it >shouldn't even be attempting to call b-tech? It is paying attention to that. The log entries are there because your system is tgrying to decide whether or not to call b-tech, and is discovering that it's not supposed to call it now. Whether or not that condition should be logged is another question...but your uucp is doing exactly what it should. -- Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can jmaynard@thesis1.hsch.utexas.edu | adequately be explained by stupidity. "It's a hardware bug!" "It's a +--------------------------------------- software bug!" "It's two...two...two bugs in one!" - _Engineer's Rap_
sean@utoday.UUCP (Sean Fulton) (10/01/90)
In article <1990Sep30.230132.7664@caen.engin.umich.edu> stealth@caen.engin.umich.edu (Mike Pelletier) writes: > >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! Check /usr/lib/uucp/Poll to make sure b-tech isn't listed. > -- Sean Fulton sean@utoday.com UNIX Today! (516) 562-5430 /* The opinions expressed above are not those of my employer */
davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr) (10/01/90)
In article <1990Sep30.230132.7664@caen.engin.umich.edu> stealth@caen.engin.umich.edu (Mike Pelletier) writes: | I have a TCP UUCP link to a system that calls me [ ... ] | uucp b-tech (9/30-16:41:05,1614,0) CONN FAILED (WRONG TIME TO CALL) That's not an error message, it's an informational message. It may be poorly chosen for wording, but it means everything is working just right. You will only get it when you have stuff queued for them, so there is a reason to log it. You can write a tiny logfile reader which drops this message and the "no work" message if you spend a lot of time reading logs. I only look at mine when there's a problem. -- bill davidsen (davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen) VMS is a text-only adventure game. If you win you can use unix.
greg@cheers.Bungi.COM (Greg Onufer) (10/04/90)
>>Any idea how I can make uusched pay attention to the fact that it >>shouldn't even be attempting to call b-tech? >>Thanks! >Check /usr/lib/uucp/Poll to make sure b-tech isn't listed. Which works as long as there isn't any work already queued for b-tech. uusched will see any existing work and try to call anyways. I don't think there is an easy way to overcome this "problem" short of buying HDB from AT&T and changing the sources. It's much easier to ignore it, since everything is working the way it's supposed to. Also, Poll may be /etc/uucp/Poll if he's using SunOS. Cheers!greg