Cameron Simpson <[EMAIL PROTECTED]> writes:
> Another possibility is that your script is dependent upon running on
> a terminal. Cron jobs do not have a controlling terminal, nor do they
> have a tty attached to any inputs or outputs.
What kind of things would do that. Do you mean something like an
explicit redirect to /dev/tty, or are there other less obvious things.
>
> Suggestion: this will be tedious, but run "strace -f" on your script
> in the cron, like:
I guess I'll still ask the question above, still, but I see now, at
least one thing that will trip that behavior.
Your guesses were good ones, and the strace worked to tip it off.
It turned out to be an elisp message contained in the loaded file,
that gets sent to screen, causing the trouble.
So I guess the cure is to make sure any things that will write to
screen are redirected. Doesn't seem to include echo statements
though.
Do you have a rough idea what things will turn up in this kind of error?
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
