cron

[Adam W.]

Sorry all cron confuses my simple mind. I need a script to run every sunday at 4:30 pm so would that entry be:

30 16 * * 7 {SCRIPTNAME}> /dev/null

[Pete Randall · Accepted solution]

Close, but Sunday is 0, not 7.


Pete

[Avinash20]

SUNDAY == 0

30 16 * * 0 {SCRIPTNAME}> /dev/null

Why do you like to redirect the output to /dev/null

Redirect the output to some file to troubleshoot in case cron does not run and

2&1>/dev/null

[Adam W.]

Roger that. Thanks Pete.

[Adam W.]

Avinash, normally I would, but this is for a command line scanner that we just have to run for our IA people to quit complaining. But since no windows files go through this machine, there shouldn't ever be any results.

[Steven Schweda]

> [...] there shouldn't ever be any results.

All the more reason to save the (null)
results somewhere. You shouldn't waste much
disk space, and it'd be easy to verify your
assumption(s).

[Dennis Handly]

>there shouldn't ever be any results.

If there are no results at all, you could just let unusual errors be mailed to you.