ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have written a script using Expect tool and obviously Tcl.
Now, this script gives an output as desired when run on the shell prompt.
However, when a cron is set to execute this script every 15 mins, it send mail saying that the program that im trying to spawn using the script is not found and that the process is invoked frm within.
If any body can help me with this issue.......it would b great.
I jus wanna know what are the checkpoints that are to b considered for the script to run in cron job.
And where am i missing out on them. Also, when do we get such an eoor message in the mail when executed in the cron.
Thanks again for ur help.
I had included the code #! /usr/bin/expect -f at the start of my script.
Also, the script is executable as it runs on the shell properly giving desired output.
What else do i need to check in that case.
tHE ERROR MESSAGE THAT I GET WHEN MY SCRIPT IS SET ON CRON IS :
bash: couldnt execute "THE spawned APPLICATION"no such file or directory.
" spawn application mo_ip"
(procedure "do_attempt" line 5)
invoked from within
" do_attempt $app_name $mo_ip"
(file ./sysusage line30 )
Here i cannot reveal the applicationinvoke and hence used APPLICATION instead.
Using the script im trying to invoke an applicationthat gives me some system details.
I give username and password to start the applicationand cmd which i want o/p.
Also note that once my application starts the prompt is APPLICATION Name >
and not the normal shell prompt $.