> /tmp/BadCron-LatestRun.log
or
| mail -s "output of last BadCron run"
or whatnot :)
Ben
On 6/14/06, Matthew Jarvis <
[EMAIL PROTECTED]> wrote:
Ben Barrett wrote:
> crontab mgt: Are you using "crontab -e"? You're not supposed to edit
> crontab 'on your own', but you can set your desired editor in your shell
> environment (vi is usually the default).
>
> debugging: Is there a mailto set? You can make a long cmd line (worse)
> or a wrapper script (better) which touches a file or does some other
> action(s) to help figure out if it is trying to run...
>
> Possibly your editor is munging the file?
>
I am using crontab -e, but it pops up the vi editor. Looking at the docs
I thought it was only the user cron files you weren't supposed to hack
into on your own, but crontab -e should be kosher. They recommend
specifying the user switch if su'd beforehand, which I'll keep in mind...
I'll investigate mailto, but not so sure mails are being sent unless
specifically done in the cron job...
Matthew S. Jarvis
IT Manager
Bike Friday - "Performance that Packs."
www.bikefriday.com
541/687-0487 x140
[EMAIL PROTECTED]
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
_______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
