🚀 go-pugleaf

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