more cron jobs

[sde]

I've dedicated this morning to understanding crontab. I am finally beginning to get it.

I set a cron on a file called stats.pl .. stats.pl is a perl script that looks at my gameserver logs and generates stats.

whenever i run ./stats.pl , it generates an error for each line it doesn't recognize .. usually there are a few errors but they're more like warnings .. it doesn't mean anything.

so here is my problem. The cronjob runs every half hour .. and it works great , but i get emailed all the errors that occur durring the stats.pl script. is there a way to make it so the system doesn't email me when errors occur within the stats.pl script itself?

[sde]

well, i was able to use regexp to filter out the lines that were causing errors in the stats.pl script. i guess this is a better solution anyhow. if there are no errors in the first place, then i won't get emails =)

[revolution]

yeah prolly good thinking , but if you dont want it to mail to ya, you can point it to a log file or to /dev/null

cmd >> log.file

if you wish not to see it at all....i found this on google for an intro into cron.......


http://www.unixgeeks.org/security/ne...ix/cron-1.html

hope it helps a little bit

[bdl]

You might try something like this, it'll redirect the output of your errors to /dev/null or to a logfile of your choosing. Remember that anything in the crontab must use absolute paths, so you can't just stick ~/cron.log into a crontab entry.

## example crontab to redirect error output

# will send to the bit bucket
0-59/1 * * * *    exec /path/to/command 2&1> /dev/null

# will send to a log file
0-59 * * * *    exec /path/to/othercommand 2&1> /home/username/logs/command.log

Hope this helps!

BTW, the 2 is the shell's standard error output channel, while 1 is the shell's standard output channel. You can use one or both to redirect output from commands.

[sde]

thanks a lot .. that makes perfect sense!