wain@seac.UUCP (Wain Dobson) (08/08/90)
What's up with this port. Suddenly, like, today, about 5PM, my
system can't get by the login. Bellow is the output from
uutry --- the important information is at the end of the script.
(Boy, from here, things like this sure can get expensive.)
mchFind called (sco)
list (rmail) num = 1
fillFlds: entered
fillFlds: returning
list (/usr/spool/uucppublic) list (/usr/tmp) num = 2
list (/usr/spool/uucppublic) list (/usr/tmp) num = 2
list (rmail) list (rnews) list (uucp) num = 3
_Request (TRUE), _Switch (TRUE), _CallBack (FALSE), _MyName (), _Commands rmail
_Commands rnews
_Commands uucp
chdir(/usr/spool/uucp/sco)
conn(sco)
Device Type ACU wanted
mlock tty2A succeeded
fixline(5, 19200)
dialer args :/usr/lib/uucp/dialTBIT:-x9:/dev/tty2A:14084250261U:19200
UUCP phone number, stripping 14084250261U
PROTOCOL phone number, got 14084250261
checkbaud claims low/high baud is 016
mdopen(): opening /dev/tty2A
set ioctl on /dev/tty2A, baudrate = 016
Syncing baud rate...aaaaSent MODEM <<ATQ4^M>>-OK
MODEM returned <<^M^JOK^M>>-OK
got OK
...done.
Resetting modem
Sent MODEM <<ATZ^M>>-OK
MODEM returned <<^J^M^JOK^M>>-OK
got OK
Syncing baud rate...aaaaSent MODEM <<ATQ4^M>>-OK
MODEM returned <<^M^JOK^M>>-OK
got OK
...done.
Setting DIAL OUT mode
Sent MODEM <<ATS66=1S110=255^M>>-OK
MODEM returned <<^J^M^JOK^M>>-OK
got OK
Setting UUCP mode
Sent MODEM <<ATS7=60S50=255S111=30^M>>-OK
MODEM returned <<^J^M^JOK^M>>-OK
got OK
DIALING ATDT14084250261
Sent MODEM <<ATDT14084250261^M>>-OK
wait for connect - timeout 243
MODEM returned <<^J^M^JBUSY^M>>-OK
got BUSY
hangup - timeout 243
Sent MODEM <<+++>>-OK
Syncing baud rate...aaaaSent MODEM <<ATQ4^M>>-OK
MODEM returned <<^M^JOK^M>>-OK
got OK
...done.
Sent MODEM <<ATH^M>>-OK
MODEM returned <<^J^M^JOK^M>>-OK
got OK
Disabling escape
Sent MODEM <<ATS2=128^M>>-OK
mdclose(): closing /dev/tty2A
Forked 11202 Wait got 11202 Status 106400
could not connect (phone is busy)
mlock tty2A succeeded
fixline(5, 19200)
dialer args :/usr/lib/uucp/dialTBIT:-x9:/dev/tty2A:14084250261U:19200
UUCP phone number, stripping 14084250261U
PROTOCOL phone number, got 14084250261
checkbaud claims low/high baud is 016
mdopen(): opening /dev/tty2A
set ioctl on /dev/tty2A, baudrate = 016
Syncing baud rate...aaaaSent MODEM <<ATQ4^M>>-OK
MODEM returned <<^M^JOK^M>>-OK
got OK
...done.
Resetting modem
Sent MODEM <<ATZ^M>>-OK
MODEM returned <<^J^M^JOK^M>>-OK
got OK
Syncing baud rate...aaaaSent MODEM <<ATQ4^M>>-OK
MODEM returned <<^M^JOK^M>>-OK
got OK
...done.
Setting DIAL OUT mode
Sent MODEM <<ATS66=1S110=255^M>>-OK
MODEM returned <<^J^M^JOK^M>>-OK
got OK
Setting UUCP mode
Sent MODEM <<ATS7=60S50=255S111=30^M>>-OK
MODEM returned <<^J^M^JOK^M>>-OK
got OK
DIALING ATDT14084250261
Sent MODEM <<ATDT14084250261^M>>-OK
wait for connect - timeout 243
MODEM returned <<^J^M^JRRING^M>>-OK
got RRING
MODEM returned <<^J^M^JRRING^M>>-OK
got RRING
MODEM returned <<^J^M^JCONNECT FAST/UUCP^M>>-OK
got CONNECT FAST/UUCP
Forked 11204 Wait got 11204 Status 0
getto ret 5
sendthem (^M)
expect: (gin:)
^Jtimed out
sendthem (^M)
expect: (gin:)
timed out
sendthem (^M)
expect: (gin:)
timed out
close caller (5)
delock(tty2A)
Call Failed: LOGIN FAILED
exit code 101
Conversation Complete: Status FAILED
TM_cnt: 0
--
Wain Dobson, Vancouver, B.C.
...!{uunet,ubc-cs}!van-bc!seac!wainwain@seac.UUCP (Wain Dobson) (08/09/90)
In article <5669@seac.UUCP>, wain@seac.UUCP (Wain Dobson) writes:
= What's up with this port. Suddenly, like, today, about 5PM, my
= system can't get by the login. Bellow is the output from
= uutry --- the important information is at the end of the script.
= (Boy, from here, things like this sure can get expensive.)
=
= wait for connect - timeout 243
= MODEM returned <<^J^M^JRRING^M>>-OK
= got RRING
= MODEM returned <<^J^M^JRRING^M>>-OK
= got RRING
= MODEM returned <<^J^M^JCONNECT FAST/UUCP^M>>-OK
= got CONNECT FAST/UUCP
= Forked 11204 Wait got 11204 Status 0
= getto ret 5
= sendthem (^M)
= expect: (gin:)
= ^Jtimed out
= sendthem (^M)
= expect: (gin:)
= timed out
= sendthem (^M)
= expect: (gin:)
= timed out
= close caller (5)
= delock(tty2A)
= Call Failed: LOGIN FAILED
= exit code 101
= Conversation Complete: Status FAILED
=
= TM_cnt: 0
Since my system got in about 3PM PST, I presume that sco was
was on overload up until about then. And, from this, I presume
that this particular machine at sco could not respond fast enough
to deal with the login when the load is high.
--
Wain Dobson, Vancouver, B.C.
...!{uunet,ubc-cs}!van-bc!seac!wainnvosd@nwnexus.WA.COM (UW West ) (08/10/90)
Gee - this sounds familiar. I just spent several bucks the same way myself. I "solved" it by trashing SCO's "dialTBIT" and using the "tbfast" dialer entry in the O'Reilly book "Managing UUCP and USENET". Works like a champ. The problem, as near as I can determine, is that the SCO system (even the one that is supposed to be 9600 baud) starts out at some lower baud rate, and then trys to step up. Well, unless you've got your TBit set just right, it'll either connect at some lower (undesired) speed, or, the SCO system will time out waiting for you to send it enough breaks to sync up. Good luck - If I get my link working, and you don't have the O'Reilly book, lemme know and I'll send you the appropriate Dialer entries (and modem settings). Clay Jackson