Re: expect command spawns incorrectly

Saturday, 28 November 2009

On 11/28/09 19:13, quoth Donald Russell:
...

 On Sat, Nov 28, 2009 at 15:47, Steven W. Orr <steveo(a)syslang.net
 <mailto:steveo@syslang.net>> wrote:

     On 11/28/09 02:43, quoth Donald Russell:
     > I am trying to use the expect program to automate an sftp process....
     >
     > The expect file begins with
     >
     > spawn sftp -oProxyCommand='....'  user@host
     > expect "password:"
     > send "sesame\n"
     > expect "sftp> "

     Try this:

     send "sesame\r"

 I'll try that, but I'm not hopeful.

 The command that is spawned fails... I get the "usage" as if all that
 was spawned was "sftp" and not the entire command. So it doesn't even
 get to the "expect password" part, regardless of whether I'm using \n or
 \r in the "send".

 And I gather there is no such character on the "spawn" line... the
 command is just taken to be the literal characters up to the end-of-line.
 Do I need to escape anything? As I mentioned, if I cut/past the command
 into a shell.. it works fine... it's just got being spawned properly by
 expect. (Or I'm doing something wrong :-( )

Ok. One last suggestion. It sounds like you might have a quoting problem.

eval spawn "sftp -oProxyCommand='....'  user@host"

I'm assuming that you are using the single quotes to contain an argument that
may have possible embedded white space. In case there is no white space, it'll
probably also work without the single quotes. By default spawn will echo what
it's doing. You can stop that via the -noecho option.

Don't forget that expect is not a language of its own. It's just an extension
to the tcl language. tcl is what provides the eval. ;-)

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net