UUCP (HDB) - urgent !
Frank Kaefer
fkk at stasys.sta.sub.org
Mon Sep 24 11:26:04 AEST 1990
Dear Readers,
I have a really severe problem with UUCP (HDB). I think this could be a
real bug of HDB UUCP and I urgently seek some advice.
Description:
If someone dials in my computer (Interactive Unix 2.2, TB2500 modem
connected with 19200 baud) with 1200 or 2400 baud, the whole thing
thing hangs after the login and the uucico has been started. After
about 1 min 45 sec. the connection is cancelled. This happens on nearly
80% of the incomung uucp-calls. Some of the callers get thousands of
"imsg> imsg> imsg>..." in their logfiles (debuglevel 9). Exactly the
SAME problem occured some time ago using a Sun Sparcstation 1+ with
SUN-OS 4.1 dialing into a SCO Xenix (80286) system and into a
Interactive System both using TB2000 modems and fixed speed at 19200
baud. So first I thought it might be a bug of SUN-OS 4.1, but now it
also happens on Interactive.
Last night the line wasn't cancelled and the uucico was doind nothing
for nearly 7 hours. This costed me quite a lot because it was a long
distance call.
Here is some uucico -x9 output:
-------
uucico: mchFind called (stasys)
uucico: list (rmail) num = 1
uucico: list (/usr/spool/uucppublic) num = 1
uucico: list (/usr/spool/uucppublic) num = 1
uucico: list (/) num = 1
uucico: list (/bin/rmail) list (/usr/bin/rnews) num = 2
uucico: _Request (FALSE), _Switch (TRUE), _CallBack (FALSE), _MyName (), _Commands /bin/rmail
uucico: _Commands /usr/bin/rnews
uucico: chdir(/usr/spool/uucp/stasys)
uucico: conn(stasys)
uucico: Device Type ACU wanted
uucico: mlock ttyF02 succeeded
uucico: filelock: ok
uucico: fixline(6, 2400)
uucico: processdev: calling setdevcfg(uucico, ACU)
uucico: gdial(Smartlink) called
uucico: expect: ("")
uucico: got it
uucico: sendthem (ATZ^M)
uucico: expect: (OK)
uucico: ATZ^M^M^JOKgot it
uucico: sendthem (ATS0=1M1^M)
uucico: expect: (OK)
uucico: ^M^JATS0=1M1^M^M^JOKgot it
uucico: sendthem (ATDP########^M)
uucico: expect: (CONNECT)
uucico: ^M^JATDP#########^M^M^JCONNECTgot it
uucico: sendthem (DELAY
uucico: ^M)
uucico: getto ret 6
uucico: expect: (ogin:)
uucico: 2400^M^J^M^M^JStasys Starnberg^M^M^Jlogin:got it
uucico: sendthem (uufips^M)
uucico: expect: (sword:)
uucico: ^M^M^M^JStasys Starnberg^M^M^Jlogin: uufips^M^M^JPassword:got it
uucico: sendthem (xxxxxx^M)
uucico: imsg >^M^JUNIX System V/386 Release 3.2^M^Jstasys^M^JCopyright (C) 1984, 1986, 1987, 1988 AT&T^M^JCopyright (C) 1987, 1988 MiLOGIN FAILED - failed
uucico: exit code 101
uucico: Conversation Complete: Status FAILED
uucico: TM_cnt: 0
-------
I had a look at the sources of HDB on SUN-OS 4.1 but I can only
guess. I think it might have something to do with negotiation of the
protocol to use (imsg.c), but I'm not sure.
So if you have any hints, PLEASE mail me or post them.
Mail to: fkk at Germany.sun.com please.
Thanks a lot in advance,
Frank
--
-------------------------------------------------------------------
| Frank Kaefer | fkk at stasys.sta.sub.org | Starnberg, West Germany |
| (Compuserve: 72427,2101) | Internet: fkk at Germany.SUN.COM |
-------------------------------------------------------------------
More information about the Comp.unix.sysv386
mailing list