Also...this bug report (Jun 2004):
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252197
for another issue quotes error output from logrotate version 3.7-1 that
identifies the log being processed when the failure occurred, yet the
version I'm using, 3.7-5, lacks this feature. Was this capability in
logrotate at one time and removed?
And, all the example emails from cron shown in these bug reports show
error text produced by logrotate itself. Fixing those error messages to
be more informative is straight forward. But there is also a problem
when processes called by logrotate write to STDERR, which triggers an
email from cron, while not necessarily returning an error exit code for
logrotate to notice. For example, I frequently see emails that look like:
/etc/cron.daily/logrotate:
Null message body; hope that's ok
which are caused when logrotate attempts to mail an empty log file.
(Apparently 'mail' doesn't return an error code in this case, which
seems reasonable.)
-Tom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
