uucico

[Chuck Karish]

[ Note changed Newsgroups: and Followup-To: headers ]

In article <219 at mlfarm.UUCP> ron at mlfarm.UUCP (Ronald Florence) wrote:
>In using the ancient (v.7 derived) uucico supplied with SCO Xenix
>386ps, version 2.2.3, we have difficulties at 2400 baud when our
>uucico starts up in SLAVE mode and has to switch in the middle of the
>transmission to MASTER mode.  As far as I can determine, our system
>does not respond correctly after the remote system sends the 'H'
>signal indicating that they have no further traffic for us.  Instead
>of the 'HN' indicating that our system has traffic for the remote, the
>remote reports in the debugging logs that it received a "backspace",
>(0x8).  The remote then signals that it has gotten a "bad read" and
>hangs up the connection.

>The problem occurs at 2400 baud with the remote (calling) system using a
>Trailblazer modem.  We do not have a Trailblazer modem.  At 1200 baud,
>with a Hayes modem on the remote, there is no problem.  If we initiate
>the connection in MASTER mode (i.e., we call them) there is no
>problem when we call the Trailblazer.

Here's what it looks line from the other end, an RT running AIX 2.2.1,
with a modern (HDB) UUCP:

 Rmtname hpda, Role MASTER,  Ifn - 5, Loginuser - root
rmesg - 'P' imsg >^PPgfx^@got Pgfx
wmesg 'U'g
send 73
nap(10) pkgetpack: Connodata=1
rec h->cntl 73
send 61
state - [INIT code a] (1)
pkgetpack: Connodata=2
rec h->cntl 61
send 53
state - [INIT code a]&[INIT code b] (3)
nap(10) pkgetpack: Connodata=3
rec h->cntl 53
state - [O.K.] (10)
Proto started g
*** TOP ***  -  role=MASTER, setline - X
gtwvec: dir /usr/spool/uucp/hpda
insert(C.hpdaC0338)  insert C.hpdaC0338 at 0
        return - 8
Wfile - /usr/spool/uucp/hpda/C.hpdaC0338,Jobid = hpdaC0338
Request: mindcrf!D.mindc771f9d6 --> hpda!D.mindc771f9d6 (root)
setline - S
wrktype - S
 wmesg 'S' D.mindc771f9d6 D.mindc771f9d6 root - D.mindc771f9d6 0666 root
send 210
rmesg - 'S' send 210
ASSERT ERROR (uucico)  pid: 7565 (5/9-9:16:09) PKXSTART ret  (0) [SCCSID: @(#)pk1.c	7.3 87/10/08 15:46:51, FILE: pk1.c, LINE: 365]

Here's the uucico log file for another host we call ( VAX 11/750 running 4.3):

uucp denali  (5/3-11:25:41,21704,0) SUCCEEDED (call to denali )
uucp denali  (5/3-11:25:47,21704,0) OK (startup)
uucp denali  (5/3-11:25:47,21704,0) BAD READ (expected 'H' got FAIL)
uucp denali  (5/3-11:25:47,21704,0) FAILED (conversation complete)
uucp denali  (5/9-9:25:07,7668,0) LOCKED (call to denali )
uucp denali  (5/9-9:25:39,7657,0) SUCCEEDED (call to denali )
uucp denali  (5/9-9:25:44,7657,0) OK (startup)
karish denali denaliC25ee (5/9-9:25:44,7657,0) REQUEST (mindcrf!D.mindc7722d44
-
-> denali!D.mindc7722d44 (karish))
karish denali denaliC25ee (5/9-9:25:45,7657,1) BAD READ (expected 'S' got
FAIL)
karish denali denaliC25ee (5/9-9:25:45,7657,1) FAILED (conversation complete)


Host hpda runs HP/UX version 3.01, according to their login banner.
I see the same problem calling VAXen running Ultrix and 4.3BSD, Suns
running various versions of SunOS, and several other types of systems.

I see the same problem whether I use a Telebit Trailblazer Plus or
a MultiTech 224E to call out.

The Trailblazer works OK in fast mode; I can dial out, and complete
a UUCP conversation successfully.

In summary, this is not a XENIX problem.  If it's a generic UUCP
problem, is there a generic cure?

	Chuck Karish		{decwrl,hpda}!mindcrf!karish
	(415) 493-7277		karish at forel.stanford.edu