This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

invalid spawn id (4)


Hey, nobody ever replied but the answer is, don't use Microsoft telnet
client with cygwin expect.  

Install cygwin telnet client ( NOT installed by default, heaven alone knows
why when they have a gazillion other things installed by default that will
only be useful to 0.000000000000000000000000000000000000000001% of the user
base )  

Anybody know how to resolve or work around this bug in expect: invalid spawn
id (4) the first time I try to something incredibly common such as use
expect to automate a telnet session.  I could not find any references to
this in the faq or archives, found one hit on google but no solution.

cygwin version: CYGWIN_NT-5.0 bwolmarans-98 1.5.4(0.94/3/2) 2003-09-12 23:08
i686 unknown unknown Cygwin
expect version: 8.4.1 ( output from info patchlevel command )
O/S version: w2k pro SP3

log:
bwolmarans@bwolmarans-98 ~
$ expect
expect1.1> spawn telnet 10.26.0.100
spawn telnet 10.26.0.100
1424
expect1.2> expect ogin
expect1.3> send bwolmarans\n
send: invalid spawn id (4)
    while executing
"send bwolmarans\n"
expect1.4>

_______________________
brett wolmarans, PSE, Spirent Communications
Cell Phone: (818) 292-3411  http://support.spirentcom.com




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]