Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Mark Fisher" To: Subject: Problems with expect logging out (going from 1.1.8 to 1.3.2) Date: Thu, 26 Jul 2001 15:28:02 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Hi, I've been using your excellent product and recently decided to upgrade to 1.3.2 from 1.1.8. However, now when I run any of my expect scripts that do any "spawn" commands, when the script finishes, it logs me out of my bash session. It doesn't matter how many levels deep I go in bash, when the expect script finishes, you get "exit" commands all the way up to logging me completely out. Here's an example script: - - - - #!/usr/bin/bash expect -f lET.expect - - - - here's the expect script [lET.expect]: - - - - set cvsRoot [ exec echo {$ETCVSROOT} ] spawn cvs -d :pserver:user AT server:$cvsRoot login expect "CVS password: " send "password\r" - - - - I've tried using #!/usr/bin/bash, and #!/bin/expect but whichever way I call it, the logout always occurs. I've rolled back to 1.1.8 and the problem goes away, yet the expect executable hasn't changed between versions, so I can only think it's a problem with the core code. Sorry if this isn't the correct area to report bugs. Yours, Mark Fisher -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/