Expect script problem


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Expect script problem
# 1  
Old 04-14-2008
Expect script problem

Hello all you scripting Gurus,

I have an expect script that gets called from an AppleScript Studio app that basically takes arguments for user name, password, and server address and then calls rsync. Everything works wonderfully, EXCEPT (there had to be one of those) if the user name starts with a t, such as "test_student", the t gets converted to a 'tab' and I instead get "[tab]est_student", which obviously won't authenticate properly.

In the following code, the problem happens at the end of the spawn line, the $login variable has the problem (although I haven't tested to see if $server and $password variables have the same problem).

I guess my question is if there is a way to make it so that expect just enters the text and doesn't try to do fancy [tabs] and such? Is there a best practice in a script like this to make sure that doesn't happen?

Thanks in advance for any help offered.

Jeff
--------

The script is as follows:

Code:
#!/usr/bin/expect --
#
# Student Backup Script
# 
# Purpose:      Based on provided login name, password and server, 
#				backup the user's Documents folder.
# Requires:     TCL and Expect extension
# Author:       Jeff Dyck
# Date:         12/18/2007
#
#               Usage format is ExpectBackup.sh username password server

# Bring in the variables...

set timeout 20

set localUser [exec whoami]
set login [lindex \\$argv 0]
set password [lindex \\$argv 1]
set server [lindex \\$argv 2]
set mode [lindex \\$argv 3]

# Begin syncronization...

spawn time rsync -a -z -E --exclude-from=/tmp/exclude.txt --progress --partial --timeout=30 -e ssh /Users/$localUser/Documents $login@$server:

expect {
       "(yes/no)?"  { send "yes\r"; exp_continue}
       "?assword:"  { send "$password\r"; exp_continue}
       }
       
# Wait for rsync to finish.
# expect eof

# Done.

exit 0

# 2  
Old 04-15-2008
I think that expect uses single backslash to escape characters, at least that's the way I do in some of my scripts. Try that and let us know.
# 3  
Old 04-15-2008
Slashes as escape characters don't seem to work...

Thanks for taking the time to offer your suggestion sysgate. I just tried modifying the script to use both forward and backward slashes, neither did what I wanted, but they had very different results...

When I used a backward slash (\) I got the following rsync command out of the expect script - the escape character seems to have just nulled the $ so I get the variable name inserted, rather than the variable's value:

Code:
spawn time rsync -a -z -E --exclude-from=/tmp/exclude.txt --progress --partial --timeout=30 -e ssh /Users/admin/Documents $login@time-od.csf.bc.ca:

When I used a forward slash (/) I got the following,which is the same as before, adding an unwanted [tab]:
Code:
spawn time rsync -a -z -E --exclude-from=/tmp/exclude.txt --progress --partial --timeout=30 -e ssh /Users/admin/Documents /	est_student@time-od.csf.bc.ca:

I even tried entering both / and \ in front of test_student right in the original command and that doesn't help either... / just adds the / in front of test_student (so does get rid of the [tab], but also doesn't give the right command) and \ doesn't seem to do anything, still end up with [tab]est_student.

What IS interesting to me is that I entered the server as 'time' simply to test if that 't' was also coming out as a [tab] - as you can see from the results, it isn't - I suspect because it's immediately behind the @ character. So perhaps this is something to do with having the variable right after a space.

So back to the drawing board. Any other ideas?

Jeff
# 4  
Old 04-15-2008
I don't understand why this script attempts to escape the variable notation ($)
preceding the argv list.
it is utterly broken this way.
example:
Code:
proc randlist {len {components "satrednfgbhj"}} {
set i 0
                      while {$i < $len} {
                            set a [expr int(1 + rand() * [string length $components] - 1)]
                             lappend ret "[string index $components $a]"
                             incr i
                       }
                       return $ret
}

foreach a [randlist 23] {puts -nonewline "No interp of escape = \\$a\nAnd interpreted = " ; eval puts "\\$a"}

Code:
Output of above:
No interp of escape = \f
And interpreted =  
No interp of escape = \n
And interpreted = 

No interp of escape = \j
And interpreted = j
No interp of escape = \e
And interpreted = e
No interp of escape = \t
And interpreted = 	
No interp of escape = \j
And interpreted = j
No interp of escape = \e
And interpreted = e
No interp of escape = \e
And interpreted = e
No interp of escape = \n
And interpreted = 

No interp of escape = \f
And interpreted =  
No interp of escape = \t
And interpreted = 	
No interp of escape = \e
And interpreted = e

Short answer: There is no need to escape the dollar sign notation and it breaks interpretation of characters during command expansion.
# 5  
Old 04-15-2008
That did it!!! Thanks ramen_noodle

ramen_noodle,

I removed the \\'s from the argv entries at the beginning of the script and that seems to have fixed the problem. It's been a while since I wrote this script originally, but I believe I grabbed that syntax from a sample script I found online, so big ooops I guess.

Thanks for pointing out what I wasn't seeing, may much good karma come your way Smilie.

Jeff
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Expect script returning string following a found expect.

I'm fairly new to scripting so this might not be possible. I am using Expect with Cisco switches and need to capture the string after finding the expect request. For example, when I issue "show version" on a Nexus switch, I'm looking to capture the current firmware version: #show version ... (0 Replies)
Discussion started by: IBGaryA
0 Replies

2. Programming

Calling another expect script inside an expect script

I have an expect script called remote that I want to call from inside my expect script called sudoers.push, here is the code that is causing me issues: set REMOTE "/root/scripts/remote" ... log_user 1 send_user "Executing remote script as $user...\n" send_user "Command to execute is: $REMOTE... (1 Reply)
Discussion started by: brettski
1 Replies

3. Shell Programming and Scripting

Problem with expect script

expect { -re "(.*)NEXT PAGE(.*)" { send "\r\n" } exp_continue (0 Replies)
Discussion started by: sagar_1986
0 Replies

4. Programming

Calling expect script inside another expect

Hi, Am very new to expect scripting.. Can You please suggest me how to call an expect script inside another expect script.. I tried with spawn /usr/bin/ksh send "expect main.exp\r" expect $root_prompt and spawn /usr/bin/ksh send "main.exp\r" expect $root_prompt Both... (1 Reply)
Discussion started by: Priya Amaresh
1 Replies

5. Shell Programming and Scripting

expect script problem

Hi, Have strange problem. When I run an expect script towards a switch, it will not work. $ ./test2 spawn ssh admin@sesafdd101 Password: Last login: Thu Dec 25 13:20:54 2008 from 172.20.96.14 ECN430/330/212 Linux, based on Wind River Linux glibc_small (standard) 2.0 Trying... (1 Reply)
Discussion started by: etxnreg
1 Replies

6. Shell Programming and Scripting

expect problem

hi all, guys i have a problem in this code... any help ? #!/usr/bin/expect if { $argc != 3 } { puts "Usage:" puts "$argv0 username oldpwd newpwd" exit } #set machine set username set oldpwd set newpwd set completed_list " " (2 Replies)
Discussion started by: b1sh0p
2 Replies

7. Shell Programming and Scripting

Need help with Expect script for Cisco IPS Sensors, Expect sleep and quoting

This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are... (1 Reply)
Discussion started by: genewolfe
1 Replies

8. Shell Programming and Scripting

Problem in expect script with password involving trailing backslash

Hi all, I have wriiten an expect script that genearates a public private key pair through ssh-keygen and then copies that key to the authorized keys file of the remote system . The problem i am facing is when i get a password for the remote machine containg a trailing backslash , the send command... (4 Replies)
Discussion started by: pradeeptyagi23
4 Replies

9. Shell Programming and Scripting

strange expect script behavior, or am i misunderstanding expect scripting?

Hello to all...this is my first post (so please go easy). :) I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
Discussion started by: v1k0d3n
2 Replies

10. AIX

Problem with expect.

Hi, I am facing a strange problem while executing a script from a solaris server. This script calls another one to execute "expect" commands on some other 40 servers (all AIX 5200). I am passing username and password to the "expect" script as arguments. My problem is that it is showing the... (4 Replies)
Discussion started by: gsabarinath
4 Replies
Login or Register to Ask a Question