Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!rutgers!att!ihlpb!gregg
From: gregg@ihlpb.ATT.COM (Wonderly)
Newsgroups: comp.bugs.sys5
Subject: Re: What does HDB "lost line errno - 0" mean?
Message-ID: <9566@ihlpb.ATT.COM>
Date: 13 Feb 89 15:01:31 GMT
References: <590@redsox.UUCP>
Distribution: na
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 19

From article <590@redsox.UUCP>, by campbell@redsox.UUCP (Larry Campbell):
> Often (maybe 50% of the time), when uucico attempts to dial out,
> it successfully opens the tty line (the DTR light on the modem comes
> on) and then gives up, closes the tty line, and retries, giving the
> debug message "lost line errno - 0".  If there's only one eligible
> tty line, this isn't a problem, since it retries and ALWAYS works
> the second time.  But if there are two (or more) eligible lines, it
> will give up on the first one and use the second one instead.

When I was at school we had a similar problem that was directly related
to reboot's.  Apparently there is one particular bit of hardware status
or perhaps a software flag that is not initialized properly by uucico
i.e. getty gets it right, but uucico doesn't.  The close(2) call
evidently did something to straighten things out so that succeeding
attempts worked.  We never really fixed the problem, we just used
kermit to attempt an outbound connection on each line right after boot.
-- 
Gregg Wonderly                             DOMAIN: gregg@ihlpb.att.com
AT&T Bell Laboratories                     UUCP:   att!ihlpb!gregg