Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!news.alpha.net!uwm.edu!math.ohio-state.edu!usc!elroy.jpl.nasa.gov!decwrl!vixie!vixie!not-for-mail From: vixie@vix.com (Paul Vixie) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: uucp failure Date: 9 Jun 1995 22:07:13 -0700 Organization: Vixie Enterprises Lines: 22 Message-ID: <3rb9a1$2ja@gw.home.vix.com> References: <3rb8el$i36@homer.alpha.net> NNTP-Posting-Host: gw.home.vix.com In article <3rb8el$i36@homer.alpha.net>, Dean Roth <Dean.Roth@mixcom.com> wrote: # BSDI 2.0 # # I've configured UUCP for incoming calls. The login works. # uucico is started and prints the right information, but always quits # after a few seconds. The log file only says "startup failure". Everything # seems to checkout. Any suggestions? What does this session look like from "uucico -x99" on the other end, or failing that, on a serial protocol analyzer? "startup failed" means your uucico sent some ^P's (uucp SYN, more or less) and got nothing back. The fact that it happens after only a few seconds indicates that the remote end may be initiating disconnect, which in turn indicates that the remote end is seeing something it doesn't like. Uucico on your end will not initiate disconnect unless a timeout (longer than "a few seconds") or loss of DCD occurs. -- Paul Vixie La Honda, CA "Illegitimi non carborundum." <paul@vix.com> pacbell!vixie!paul (dont let the bastards grind you down)