Search Results

script:
#!/usr/bin/expect -f
setenv PATH "/usr/bin:/usr/local/sbin"
spawn "/tms6/scripts/tms6-snapshot.sh"
expect "Select Operation" { send "1\r" }
expect "Select TMS6 Snapshot Type" { send...

I've tried using bot env and setenv and both have the same outcome. I'm questioning that it's an environment problem as both the cron job and the command line reference the /usr/bin/ directory

I'll give that a shot now. In researching it looks like the syntax is a little different but I'll work through it and update. Thank you for the help btw.

Any other ideas on this one if its not the environment? This is the final hurdle I need to jump to close out a project.

---------- Post updated at 08:46 AM ---------- Previous update was at 08:41...

Rudi, I tested your theory and I believe you are correct with the path/environment. I ran the following:

command line: ...

I picked up that line with the TH in the path from another thread in a futile attempt to resolve this. With your suggested changes the script still doesn't run via cron and now it no longer runs on...

Thanks for the reply Corona688. I must've pasted an older version of the script. Either way, I removed the # but the script continues to give no output or result. Just the same cron log entry showing...

Hello All,

I'm having an issue getting an expect script to run as a cron job. The script executes fin if I run it from the command line but I get nothing when trying to run it as a cron job....