Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!sundc!rlgvax!dennis From: dennis@rlgvax.UUCP (Dennis Bednar) Newsgroups: comp.unix.questions Subject: Re: Help with UUCP Message-ID: <335@rlgvax.UUCP> Date: Wed, 14-Jan-87 18:54:59 EST Article-I.D.: rlgvax.335 Posted: Wed Jan 14 18:54:59 1987 Date-Received: Thu, 15-Jan-87 04:12:20 EST References: <2051@brl-adm.ARPA> Organization: Computer Consoles Inc, Reston VA Lines: 32 Summary: 3 answers to your uucp problems In article <2051@brl-adm.ARPA>, kvancamp@ARDEC.arpa (Kenneth Van Camp -FSAC-) writes: > RETRY TIME (3300) NOT REACHED Try removing the STST.machine file, in /usr/spool/uucp. If you don't, a soon attempt to run uucico will fail. > but does anyone know what the -r1 does? The -r1 sets the mode to "master" or "caller", as opposed to "slave" or "server". The "role" variable inside uucico is by default 0 (slave), and -r1 causes the variable to be set to 1 (master). > 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. Also try putting an entry in the crontab file to run uucico periodically. If uucico exhausts the queue, and you queue up new information, the new uucico started will not be able to file transfer because of the short time (the 3300 you mentioned). Unless you type in another uucp or mail or postnews command, there is nothing to "poke" uucico to tell it to start file transfering again. This is because uucico is *not* a daemon, but rather, a one-shot program. -dennis -- -Dennis Bednar {decvax,ihnp4,harpo,allegra}!seismo!rlgvax!dennis UUCP