On Sat, Sep 03, 2005 at 12:10:35AM -0400, Tom Metro wrote: > 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?
That's because it's a shared script. Upstream had fixed those, but had forgotten the single rotated file case. > 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.) Difficult to fix that one, as that depends on the behaviour of the mail program. If you think that zero length logs shouldn't be mailed, I'd suggest opening a new bug about that. The behaviour of programs in a script is not something that logrotate can control. -- Paul Martin <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
