roth2@hulaw1.harvard.edu (06/12/91)
I interrupt the ethereal 88K dialogue to pose the following modest query: In order to manually poll my uucp host after the crontab poll fails (i.e., it gets a busy signal) I must use the debugging option in order to over-ride the "retry time not reached" message. The poses a problem to my uucp host, as it creates a file which he must erase. He tells me, however, that he knows there is a way to do a manual poll without debugging immediately after a failed attempt. Does anyone know how to do this? Perhaps the answer is to reset the default retry to to zero somehow? Make any sense? Thanks in advance for the help. I now return you to the vertiginous 88K discussion already in progress. Tony Roth -------------------------------------------------------- NeXTMail to all addresses: tony%cyrano@merk.com tony%cyrano@uunet.uu.net ...uunet!cyrano!tony roth2@hulaw1.harvard.edu (as a last resort only!)
glenn@heaven.woodside.ca.us (Glenn Reid) (06/13/91)
roth2@hulaw1.harvard.edu writes > In order to manually poll my uucp host after the crontab poll fails (i.e., it > gets a busy signal) I must use the debugging option in order to over-ride the > "retry time not reached" message. The poses a problem to my uucp host, as it > creates a file which he must erase. He tells me, however, that he knows there > is a way to do a manual poll without debugging immediately after a failed > attempt. Does anyone know how to do this? Just remove the file /usr/spool/uucp/STST/remotehost before you try the poll again. Here's a C-shell alias I use to "kick" a UUCP connection that didn't work for whatever reason: alias kick 'rm -f /usr/spool/uucp/STST/\!*; /usr/lib/uucp/uucico -r1 -s\!*' usage: kick <hostname> And I'm sure this will run much faster on an 88110 processor :-) -- Glenn Reid RightBrain Software glenn@heaven.woodside.ca.us NeXT/PostScript developers ..{adobe,next}!heaven!glenn 415-326-2974 (NeXTfax 326-2977)