Results 1 to 2 of 2

Thread: expect program executing next command before existing one finishes

  1. #1
    Join Date
    Feb 2014

    expect program executing next command before existing one finishes

    Hie guys, im new to scripts so i just thought of automating some ssh functions using "expect" and "cron". some people dump files into their server daily so i have to collect them daily and delete the files when i finish copying them. my problem is that expect is sending the next command before the running command finishes excecuting. for example,

    my script follow the secquence

    1) ssh into remote host --->
    2) change directory into folder with file -->
    3) compress all csv files into tar.gz file -->
    4) copy tar.gz file to remote host i.e (to my server) -->
    5) delete csv and tar.gz file when done downloading the file to my server.

    so before the comptression of files is complete, im seeing on the terminal the copy command being sent, followed by the delete command, to the extent that when the compression finishes, there is no other command to execute.
    HTML Code:
    spawn ssh ftp@
    expect "*sword.*"
    exp_send "password\r"
    expect "$ "
    exp_send "cd /srv/network_stats/stats\r"
    expect "$ "
    exp_send "tar -czvf compressed_files.tar.gz *.csv\r"
    expect "$ "
    exp_send "rm -rf *.csv\r"
    expect "$ "
    exp_send "scp *.tar.gz  ftpuser@\r"
    expect "*sword.*"
    exp_send "mypassword\r"
    expect "$ "
    exp_send "exit\r"

    what am i doing wrong?

  2. #2
    Join Date
    Jul 2007
    Ubuntu 14.04 Trusty Tahr

    Re: expect program executing next command before existing one finishes

    why don't you split compression and download into 2 different cron jobs with a delay between them? 23:30 compression, 23:45 download.

    Your expect approach looks incredibly fragile because it tries to mimick human interaction when none is really needed. I'd set up a script on the other side to do things in order to eliminate the need for doing everything in expect (open ssh connection, run script, done). The script could also be cronned so you would be able to copy stuff with scp right off the bat.

    my idea
    ftp machine: cron job at 23:30
    local machine: cron job at 23:45 (or directly scp ....)
    Last edited by Vaphell; February 26th, 2014 at 06:22 PM.
    if your question is answered, mark the thread as [SOLVED]. Thx.
    To post code or command output, use [code] tags.
    Check your bash script here // BashFAQ // BashPitfalls


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts