| dbrett7@gmail.com 2007-08-27, 8:35 pm |
| Unfortunately there is no errors, and when you do 'ps' all the
processes are still running. Nothing gets done. It is nothing more
than a guess, because the file does not get updated.
thanks
On Aug 27, 1:14 pm, Mark Janssen <mpc.jans...@gmail.com> wrote:
> On Aug 25, 4:55 pm, dbre...@gmail.com wrote:
>
>
>
>
>
>
>
>
>
>
> How did you guess this is where your problem is? Any proof of that?
> Some suggestions:
>
> 1) Add some debugging output and redirect stdout to a file in the
> crontab so you can determine exactly where the script is stalling.
> 2) add the line:
>
> log_user 1
>
> at the beginning of your script. This will tell Expect to display
> debugging output reporting its progress.
> 3) Report back the results.
>
> One additional thing, processes running in a crontab have a different
> environment than processes started from the shell. It could be the
> case that because you don't have a TERM variable set for instance, the
> remote process actually never displays, --More-- and end when run from
> the crontab. You could check this by replacing the while loop with:
>
> while 1 {
> expect -re .*
> puts $expect_out(buffer)
>
> }
>
> and check if --More-- and end actually show up in the crontab (again
> by redirecting to a file)
>
> Mark
|