|
I have a cronjob that's giving me
action.
I have a job schedules, and it's successfully
running every 5 mins. This creates a mountain of log files which I'd like
to ignore, because they are irrelevant. The job just checks a mail queue,
and retries anything that might be stalled for any reason.
Anyway, I appended "> /dev/null" onto the end of the line
in the crontab, but it's still giving me the output. I know that it
shouldn't, I've used this before.
Does anyone have any suggestions? I've seen a
few people appending "> /dev/null 2>&1" but since I'm not too sure
what this does, I'm wondering if it could be explained...
Thoughts or suggestions appreciated.
Thanks
Kev.
|
- Re: (clug-talk) Crontab logging Kevin Anderson
- Re: (clug-talk) Crontab logging Mark Lane
- Re: (clug-talk) Crontab logging HJ Hornbeck
- Re: (clug-talk) Crontab logging Jesse Kline
- RE: (clug-talk) Crontab logging Curtis Sloan
- Re: (clug-talk) Crontab logging Kevin Anderson
- Re: (clug-talk) Crontab logging Trevor Lauder
- RE: (clug-talk) Crontab logging Curtis Sloan
- RE: (clug-talk) Crontab logging Mark Lane
- RE: (clug-talk) Crontab logging Jesse Kline
- RE: (clug-talk) Crontab logging Trevor Lauder
