Path: utzoo!attcan!uunet!ncc!alberta!att!occrsh!occrsh.ATT.COM!rjd
From: rjd@occrsh.ATT.COM
Newsgroups: comp.sys.att
Subject: Re: Bug in HDB uucp
Message-ID: <144800030@occrsh.ATT.COM>
Date: 12 May 88 18:31:00 GMT
References: <8450@netsys1.UUCP>
Lines: 31
Nf-ID: #R:netsys1.UUCP:-845000:occrsh.ATT.COM:144800030:000:1529
Nf-From: occrsh.ATT.COM!rjd    May 12 13:31:00 1988


:> I think I have discovered a bug..
:> 
:> When dialing 5 or 6 entries for the same site,all unsuccessful,
:> uucico suddenly fails with "Can't find hayes in Dialers file".
:> The log says "failed generic call to gdial"..  Anyone else
:> ever see this?
:
:	I have seen a similar problem on a few past occasions:  With
:4 entries for a site (this is an exact description), sometimes HDB
:would fail to try ALL of them; i.e., it would quit after trying just
:the first 2 or 3 entries.  This is on 3B2's running SVR2.2.

  I have no answer for Len's question about the "Can't find hayes in Dialers
file", but I may have an answer for Larry's problem. NOTE: The following
*opinions* are based on experience with about 50 personal entries and the
1800 Action Central entries that I use, but I have *not* perused the source
to verify it.

  For the uucp to try another entry in the Systems file, it must have failed
in the Dialers file chat script, rather than the Systems file chat script.
This makes sense, as the chat script in the Systems file is meant for the
login sequence only, whereas the Dialers chat script is intended to get
the host machine hooked up to the remote machine.  It follows suit that, if
you were successful in getting to the remote machine and the login sequence
(read: Systems file chat script) failed, that there is no point in trying
a different path to connect to the remote machine.  You might also notice that
if the System file chat script fails, it reports "LOGIN UNSUCCESSFUL", or
some such.

Randy