briand@rfengr.com (Brian Dear) (06/03/91)
When my NeXTcube ('040, 2.1, 340MB, OD) dials to my local UUCP
host, it often fails to connect. Part of this is probably due
to the UUCP host, but anyways. One thing I notice is that upon
connecting, I get:
GOT: CONNECT 2400hayes ok
login called
wanted "gin:"
got: ?
send "BREAK"
ioctl 0.300000 second break
wanted "gin:"
~got:?
and so on...
But it takes like 45 or 60 seconds for the NeXT to send a BREAK. Why?
How can I set it such that when the NeXT connects to the other machine,
it sends out its first break right away (if need be, i.e., if it didn't
receive the "gin:" string). And keep on sending breaks maybe every
few seconds. 5 to ten second pauses are one thing, but waiting 5 to 6
minutes trying to connect (only to get a timeout from the NeXT) is
just not acceptable. Any suggestions for altering the UUCP chat script?
Or other settings/config defaults/etc.?
(I would like to add that when I dial up the UUCP host from my
PC, using Procomm, I get a CONNECT but no login prompt (the UUCP
host is prolly usually answering at a baud rate other than my
modem's 2400 speed) and if I do an Alt-F7 (tell Procomm to send
a break) I *immediately* get the login prompt from the UUCP
host. So it's hard to place blame on the other machine. This
*seems* to be a NeXT problem.)
Brian Dear Coconut Computing, Inc. brian@coconut.com