I have a crontab entry that goes out to 12 servers each day and gathers statistics about their dayend processing. The script goes to both HP and AIX servers (which shouldn't make a difference, I don't think). We output the job to a log file. Some weeks, the job will run successfully every day and then the next week, it will only run or gather stats one day. All that is posted to the log file when no stats are gathered is the word "exit". There are no errors in the /var/spool/cron/log file - you can see the job kick off and then a couple of minutes later in the log you see PID successful.

I was just wondering if there was a way to capture more information when the job doesn't run in place of the "exit" that gets posted. Or if there is somewhere else on the system I can look for errors.

Thanks

Try the mailbox for the user who owns the crontab. This is where any untrapped messages go.
Failing that the script will need improving.

Okay, thank you. The job is run as root and there were no emails about this job so I guess I will start working on the script.
Thanks again for your reply.