UUCP blues on a TS.

Thread View: comp.mail.uucp

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Bob Chalmers Sun, 04 Dec 1994 03:44

#5311

Author: Bob Chalmers
Date: Sun, 04 Dec 1994 03:44

40 lines
2674 bytes

I've got those uucp blues..  I am running a SCO server, with a
Stallion Easy Communication Server on it. It's an intelligent 
Terminal Server basically. 
I can uucp to the SCO machine, tty2A, no problems, it fires 
straight in no worries.
The TS is set up on port 8 as a bi-directional modem etc and I can
dial straight into it. Login, and password come up fine, and it lets me
access the host as a login no problems.  However,..............
When I uucp to the same connection, it gets as far as taking the login
response, and then simply waits forever until it times out.

uucp gold DEBUG: fcsend: Writing "ATQ0V1E0&Q5&K3M0DT" \D "xxxxxxxxxxxx\r"
uucp gold DEBUG: icexpect: Looking for 13 "CONNECT 19200"
uucp gold DEBUG: icexpect: Got "CONNECT 19200" (found it)
uucp gold DEBUG: fcsend: Writing "\r\r"
uucp gold DEBUG: icexpect: Looking for 6 "login:"
uucp gold DEBUG: icexpect: Got "\r\n\r\r\ngold\r\n\n\rWelcome."
uucp gold DEBUG: icexpect: Got "\n\r\r\ngold!login:" (found it)
uucp gold DEBUG: fcsend: Writing "earth\r"
uucp gold DEBUG: icexpect: Looking for 5 "word:"
uucp gold DEBUG: icexpect: Got " " (timed out)
uucp gold ERROR: Timed out in chat script
uucp gold DEBUG: fcsend: Writing sleep sleep "+++" sleep sleep "ATZ0\r" sleep
uucp gold DEBUG: Call failed: 3 (LOGIN FAILED)

I actually had it working fine once, now.... not a chance, and I have 
tried every thing i know.
What is uucp doing, that it wont let the login proceed ?

Help please.

cheers,
Bob
-- 
...........................  ................  .............................
|  Robert Chalmers.         ,-._|\*<-Mackay    robert@nanguo.cstpl.com.au  |
|   cstpl.com.au.          /      \ FAX: +61 79 524032  PH: +61 79 524395  |
| International Access.    \_.-\__/  *Info,	        info@cstpl.com.au  |
| AARNet Value Added Reseller.	 v   *Sales,  	        sales@cstpl.com.au |
|---MIME CAPABLE------* ao zhong you yi wan sui *--------------------------|

Re: UUCP blues on a TS.

#5310

Author: Brian J. Murrell
Date: Sun, 04 Dec 1994 18:25

38 lines
2474 bytes

In article <D09p2H.I3s@nanguo.cstpl.com.au>,
Bob Chalmers <earth@nanguo.cstpl.com.au> wrote:
>I've got those uucp blues..  I am running a SCO server, with a
>Stallion Easy Communication Server on it. It's an intelligent 
>Terminal Server basically. 
[ deletion ]
>When I uucp to the same connection, it gets as far as taking the login
>response, and then simply waits forever until it times out.
[ more deletion ]
>uucp gold DEBUG: icexpect: Looking for 6 "login:"
>uucp gold DEBUG: icexpect: Got "\r\n\r\r\ngold\r\n\n\rWelcome."
>uucp gold DEBUG: icexpect: Got "\n\r\r\ngold!login:" (found it)
>uucp gold DEBUG: fcsend: Writing "earth\r"
>uucp gold DEBUG: icexpect: Looking for 5 "word:"
>uucp gold DEBUG: icexpect: Got " " (timed out)

try changing your chat script to put a delay (\d i believe) before your
login string.  Something like...

ogin:--ogin: \dearth word: earth_password

The problem is that login() flushes the input buffer after printing the
"login:" prompt to the terminal and then waits for input.  Automatic login
procedures are usually too quick for login() and send their login string
before login() actually flushes the buffer, thereby throwing away what you
sent ("earth" in your case).

There is also a "yet to be documented" switch (-n I think) which you can
put on getty() to supress the buffer flush, but I don't remember the details.
Perhaps somebody can remind us.  The delay should work for you though.

b.

-- 
Brian J. Murrell                                               brian@ilinx.com
InterLinx Support Services, Inc.                              brian@wimsey.com
North Vancouver, B.C.                                             604 983 UNIX
        Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD

Re: UUCP blues on a TS.

#5309

Author: Scot Harkins
Date: Sun, 11 Dec 1994 04:17

22 lines
1644 bytes

Greetings!

Brian J. Murrell (brian@ilinx.com) wrote:
: The problem is that login() flushes the input buffer after printing the
: "login:" prompt to the terminal and then waits for input.  Automatic login
: procedures are usually too quick for login() and send their login string
: before login() actually flushes the buffer, thereby throwing away what you
: sent ("earth" in your case).

A valid observation.  Even when I dial in, if I type too soon the login 
fails while the buffer flushes my first keystrokes.  I usually end up 
getting 'oot' echoed back.

Have fun!
Scot


-- 
Scot Harkins (KA5KDU)   |Lord Scot MacFin      |Brand new Daddy!
Renton, WA, USA         |Porte de L'eau, AnTir |Herald at Large.
scoth@cyberspace.com    |Real men use sh & vi  |Native Texan!
Systems Administrator, Thurman Industries, Kirkland, WA, USA

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads