Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!brl-adm!adm!kvancamp@ARDEC.arpa From: kvancamp@ARDEC.arpa (Kenneth Van Camp -FSAC-) Newsgroups: comp.unix.questions Subject: Help with UUCP Message-ID: <2051@brl-adm.ARPA> Date: Mon, 29-Dec-86 15:03:15 EST Article-I.D.: brl-adm.2051 Posted: Mon Dec 29 15:03:15 1986 Date-Received: Mon, 29-Dec-86 21:51:14 EST Sender: news@brl-adm.ARPA Lines: 34 I have just recently established a UUCP connection between two of our Unix systems, and am having a few problems I was hoping someone could help with: My system admin's documentation on installing UUCP gives the following hint for debugging connections by first using the -r option on the UUCP command to force the request to be queued, instead of trying to execute immediately, then invoking Uucico as: /usr/lib/uucp/uucico -r1 -x4 -ssystem This works very nicely the first time I try it, and it has helped immeasureably in troubleshooting my send/expect pairs in the L.sys file. Unfortunately, this command only works once; the second time I get the error message: RETRY TIME (3300) NOT REACHED which I can only get rid of by rebooting the system (or so it seems). I was under the impression that using the notation 'Any' (minus the quotes, of course) for the time in the L.sys entry would allow me to retry a UUCP command any time I like. I also tried 'Any,1' to force the minimum retry time to be one minute, with the same results. I think a lot of my confusion could be solved if I had a man page entry on Uucico. I work on three different Unix systems, and none of them has one. I understand that the -x4 flag above sets the debugging level, but does anyone know what the -r1 does? And is there another flag that will take care of my retry time error? Finally, since 'Any,1' sets the minimum retry time for UUCP, is there any way to set a MAXIMUM retry time? That is, how can I force UUCP to try again every five minutes (say) until the queue is empty? My transfers have been occurring, but they have been taking horribly long to occur and often do not seem to be retried until I reboot. I appreciate any help or advice. Thanks. --Ken Van Camp