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: <20040823144051.22937.qmail@web41206.mail.yahoo.com> Date: Mon, 23 Aug 2004 07:40:51 -0700 (PDT) From: Andrew Louder Subject: Latest ssh can not be spawned from expect. To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes To whom it may concern: My script works on a older cygwin software: expect == 5.26 ssh == OpenSSH_3.6.1p2 My script fails on a current cygwin software: expect == 5.26 ssh == OpenSSH_3.8.1p1 The symptons show that expect can not recognize the ssh output, so I will be prompted over and over again for the password. Also note, if I ssh from the older installation to the current installation, then my script works again. It appears the problem lives is term compatibility. Andy PS. Here is my script and example successfull execution: $ cat t.exp #!/usr/local.bin/expect -f set timeout 60 send_user "Logging into pilot 172.18.64.110\n" if {[catch {spawn ssh root AT 172 DOT 18 DOT 64 DOT 110}] != 0} { send_user "PwrSlammer.exp could not telnet to 172.18.64.110\n" exit -1 } expect "Are you sure you want to continue connecting*" { send "yes\r" ; exp_co ntinue } \ "password:*" { send "pillar\r" ; exp_continue } \ "#" { } Administrator AT coibmtest1 /tmp $ expect -f t.exp Logging into pilot 172.18.64.110 spawn ssh root AT 172 DOT 18 DOT 64 DOT 110 root AT 172 DOT 18 DOT 64 DOT 110's password: Last login: Sat Aug 21 13:19:54 2004 from coibmtest1.test.pillar [root AT pilot1 root]# __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail -- 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/