chat script time outs
Bret A. Johnson
Udo Munk
: I have finaly gotten UUCP to dial out. However, The chat
: script times out. Here is some output of UUCICO -xchat:
: system mwcbbs
: time Any
: baud 38400
: port com4fl
: phone 17085590452
: chat "" \n in:-\n-in: nuucp word: public word: XXXXXXXXXX
: protocol g
: protocol-parameter g window 3
: protocol-parameter g packet-size 64
: myname bjohns
: request yes transfer yes
: remote-send /usr/spool/uucppublic /tmp
: remote-receive /usr/spool/uucppublic /tmp
: commands rmail uucp rnews
Add a line: chat-timeout 60, this should help.
--
Udo Munk, Oberstr. 21, 41460 Neuss, Germany
privat: u...@umunk.GUN.de CIS: 100021,2515
work: u...@mwc.com
Lou Sortman
>Bret A. Johnson (br...@bjohns.win.net) wrote:
>: script times out. Here is some output of UUCICO -xchat:
[...]
>
>Add a line: chat-timeout 60, this should help.
Ok, here's a harder one.
How can I keep the g protocol from barfing when I am dialing into a site where
the modem is on a terminal server?
I don't have access to configure the terminal server or the modem that I'm
dialing into.
I can get all of the way through the chat, but it dies in the file transfer
protocol.
I tried the f protocol too with no success.
The i protocol isn't available on the other machine.
When I run sz -TT to test for data transparency, it looks fine.
When I do zmodem transfers from the same system, sometimes it works fine, and
sometimes I need to specify the -e flag (escape control characters).
Is this a hopeless endeavor?
--
l...@tfnet.ils.unc.edu (Lou Sortman)
Coherent User, Denture Wearer
Hi Dad!
dfi...@colornet.com
>I have finaly gotten UUCP to dial out. However, The chat
>script times out. Here is some output of UUCICO -xchat:
>
>uucp mwcbbs (12/15-21:05:36,688,0) DEBUG: fcsend: Writing "ATQ0 V1 E1 DT " \D "17085590452\r"
>uucp mwcbbs (12/15-21:05:36,688,0) DEBUG: icexpect: Looking for 7 "CONNECT"
>uucp mwcbbs (12/15-21:05:36,688,0) DEBUG: icexpect: Got "\r\nCONNECT" (found it)
>uucp mwcbbs (12/15-21:05:58,688,0) DEBUG: fcsend: Writing "\n\r"
>uucp mwcbbs (12/15-21:05:58,688,0) DEBUG: icexpect: Looking for 3 "in:"
>uucp mwcbbs (12/15-21:05:58,688,0) DEBUG: icexpect: Got " 38400\r\n\r\n\007Coherent 386 login:" (found it)
>uucp mwcbbs (12/15-21:05:58,688,0) DEBUG: fcsend: Writing "nuucp\r"
>uucp mwcbbs (12/15-21:05:58,688,0) DEBUG: icexpect: Looking for 5 "word:"
>uucp mwcbbs (12/15-21:05:58,688,0) DEBUG: icexpect: Got " " (timed out)
>uucp mwcbbs (12/15-21:06:08,688,0) ERROR: Timed out in chat script
>uucp mwcbbs (12/15-21:06:08,688,0) DEBUG: fcsend: Writing sleep "+++" sleep "ATH0 V0 E0 Q1\r"
[...]
I don't have 4.2 yet, but had a similiar problem talking to an SCO ODT system.
I had to put a pause before sending the password.
However, I had never gotten Taylor to talk to UUPSI. Is there anyone out there
who managed to get this working ? I was using Taylor 1.04 with the r70 kernel.
I can't believe I'm the only Coh user who is using UUPSI.
Regards,
Dave.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= David E. Filip UUCP : dfi...@colornet.com =
= ColorNet Information Systems CIS : 76430,3111 =
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= The belief of what makes a good operating system is generally based more =
= in theology than technology ... and, of course, my belief is right ! =
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Bob Chalmers
: script times out. Here is some output of UUCICO -xchat:
DEBUG: fcsend: Writing "ATQ0 V1 E1 DT " \D "17085590452\r"
DEBUG: icexpect: Looking for 7 "CONNECT"
DEBUG: icexpect: Got "\r\nCONNECT" (found it)
DEBUG: fcsend: Writing "\n\r"
DEBUG: icexpect: Looking for 3 "in:"
DEBUG: icexpect: Got " 38400\r\n\r\n\007Coherent 386 login:" (found it)
DEBUG: fcsend: Writing "nuucp\r"
DEBUG: icexpect: Looking for 5 "word:"
DEBUG: icexpect: Got " " (timed out)
ERROR: Timed out in chat script
DEBUG: fcsend: Writing sleep "+++" sleep "ATH0 V0 E0 Q1\r"
Is your modem set to auto-baud select, usually &Q6? That way you can have
a different telco line speed to that between the modem and computer.
Although that doesn't look like the problem here.
: system mwcbbs
: time Any
: baud 38400
: port com4fl
: phone 17085590452
: chat "" \n in:-\n-in: nuucp word: public word: XXXXXXXXXX
\r\d\r in: nuucp
should be a little more responsive,
I'd be inclined to use a non-flow controlled port. UUCP does it's own flow
control. and,
This is the bit that you are falling over on. mwcbbs takes some time to answer
usually.
>>>>>> you should add the line
chat-timeout 60
so that the thing waits for the called system to respond.
The default timeout is to short. It might help to put the
same line in your 'dial' file as well. It seems to respond to
both places depending on its needs. Thats 60 seconds. You can try increasing
that.
: protocol g
: protocol-parameter g window 3
: protocol-parameter g packet-size 64
you should try removing the above protocol stuff, and replacing it
with
protocol igj
as the i protocol is MUCH faster, and bi-directional. You don't need
to put window sizes etc in. Accept the defaults.
: request yes transfer yes
: remote-send /usr/spool/uucppublic /tmp
: remote-receive /usr/spool/uucppublic /tmp
: commands rmail uucp rnews
The above are all defaults, so you dont really need to put them in!
: Thank you for all your help.
Hope that gets it for you.
Bob
--
____________________________________________________________________________
|Robert Chalmers.(Li Bai) ,-._|\*<-Mackay ea...@nanguo.cstpl.com.au |
|Coherent E-Mail Bureau. / \*<-Brisbane pa...@cstpl1.cstpl.com.au |
| Sales +61 79 524395 \_.-\__/ *Mail->News, coh...@cstpl.com.au |
|UUCP nanguo!earth +61 79 524527 v *Info Server, in...@cstpl.com.au |
| cstpl1!paul +61 7 8011736 *uucp, in:nuucp rd:uupublic ~/INFO|
|----------------------* ao zhong you yi wan sui. *------------------------|
Andrew MacIntyre
>Is your modem set to auto-baud select, usually &Q6? That way you can have
>a different telco line speed to that between the modem and computer.
>Although that doesn't look like the problem here.
>: system mwcbbs
>: time Any
>: baud 38400
>: port com4fl
>: phone 17085590452
>: chat "" \n in:-\n-in: nuucp word: public word: XXXXXXXXXX
> \r\d\r in: nuucp
> should be a little more responsive,
>I'd be inclined to use a non-flow controlled port. UUCP does it's own flow
>control. and,
>This is the bit that you are falling over on. mwcbbs takes some time to answer
>usually.
Most modems will drop carrier if the buffer overflows, so not using hardware
flow control is not a good move unless you're using the same baud rate from
CPU to modem as modem to modem.
Andrew MacIntyre
<and...@happy.dotc.gov.au>
These thoughts are mine alone ...
Udo Munk
: Ok, here's a harder one.
: How can I keep the g protocol from barfing when I am dialing into a site where
: the modem is on a terminal server?
Well, I don't know what the problem with the terminal server is, but you
could increase the protocol timeouts, so that uucico doesn't disconnect
to early, when there is a problem on the other side.
The top few lines from my /usr/lib/uucp/sys:
protocol iGg
protocol-parameter g window 7
protocol-parameter g packet-size 512
protocol-parameter g timeout 20
protocol-parameter G window 7
protocol-parameter G packet-size 512
protocol-parameter G timeout 20
protocol-parameter i window 16
protocol-parameter i packet-size 1024
protocol-parameter i timeout 20