Cronjobs on long-unattended servers

This is probably obvious to the system administrators out there, but it's interesting to note the impact when you don't pipe the output (both stdout and stderr) of a cron job to /dev/null.

Every time the task runs, it emails its output to the account owner. If this happens every 5 minutes, that's 288 times a day or about a hundred thousand after a year.

If you intend that server -- and the cronjob running on it -- to be running for a long time without intervention, do yourself a favor and send the output to the null device. Or else you'll wind up with gigabytes in /var/mail.

Comments

Post new comment

All comment submissions must follow the Comment Policy. Your words remain your own and you are responsible for them. If you don't like the captcha, Login to a user account. You can login with OpenID too..
The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <img> <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <embed> <blockquote> <p> <iframe> <div> <span> <tt>
  • Lines and paragraphs break automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
u
r
S
n
3
h
T
Enter the code without spaces and pay attention to upper/lower case.