new policy topic: cron jobs (sec 3.5)
I would like to make it policy that cron jobs do not emit any message
during normal processing. Here's a possible wording:
Any cron job which is installed should not emit any messages to
STDOUT or STDERR during normal processing. Messages should
only be emitted if an unexpected condition occurs during execution.
Cron jobs are allowed to log messages to a log file, i.e., use
syslog() under any conditions deemed appropriate by the maintainer.
RATIONALE:
Ever night I get the following email, and it is very annoying.
| From: root@burrito.onshore.com (Cron Daemon)
| To: postgres@burrito.onshore.com
| Subject: Cron <postgres@burrito> /usr/lib/postgresql/bin/do.maintenance
| Date: Thu, 19 Feb 1998 04:00:07 -0500
|
| Vacuuming template1
.....A. P. Harris...apharris@onShore.com...<URL:http://www.onShore.com/>
Reply to: