Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <629E717C12A8694A88FAA6BEF9FFCD4403230E67@brigadoon.spirentcom.com> From: "Wolmarans, Brett" To: "'cygwin AT cygwin DOT com'" Subject: invalid spawn id (4) Date: Mon, 1 Mar 2004 16:33:00 -0800 MIME-Version: 1.0 Content-Type: text/plain 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 AT 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/