Bug 56191 - logwatch is too noisy
logwatch is too noisy
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: logwatch (Show other bugs)
7.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-11-13 14:25 EST by Michal Jaegermann
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-11-13 14:26:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch to kill empty reports from logwatch (2.21 KB, patch)
2001-11-13 14:26 EST, Michal Jaegermann
no flags Details | Diff

  None (edit)
Description Michal Jaegermann 2001-11-13 14:25:44 EST
Description of Problem:
'logwatch.pl' script has a nasty habit of writing empty reports when
there is nothing to report.  This is actually a security issue because
after short while recipients stop paying attention to a constant noise
from logwatch or it gets turned off.

Attached patch can be used to address that particular problem.
If, for some reasons, empty reports are desirable in some situations
then an initial value of a variable '$printing' can be made overridable
on a command line and/or in configuration.

'logwatch' in general reports too many "regular" events ('sendmail'
activities, which can be a great PITA on a machine which handles
reasonable amounts of mail, or regular logins via ssh) and is not
that easy, appearances in /etc/log.d/ to the contrary, to shut it up
but this patch can be at least some beginning.
Comment 1 Michal Jaegermann 2001-11-13 14:26:48 EST
Created attachment 37443 [details]
patch to kill empty reports from logwatch
Comment 2 Elliot Lee 2001-11-13 14:34:06 EST
I agree that logwatch is too noisy, but fixes like this that change the basic
output of the program probably should just go upstream to the author
<kirk@kaybee.org> and we will need to pick them up at some point.

Note You need to log in before you can comment on or make changes to this bug.