Bug#254542: [Logcheck-devel] Bug#254542: rng-tools: Bad non-error message [PATCH]

Henrique de Moraes Holschuh hmh at debian.org
Wed Jun 16 15:42:28 UTC 2004


On Wed, 16 Jun 2004, maks attems wrote:
> tags 254542 pending 
> thanks
> 
> On Wed, 16 Jun 2004, Kapil Hari Paranjape wrote:
> 
> ..
> > I should have read the logcheck documentation more carefully before
> > filing the bug. I didn't want to start a controversy...
> > 
> > Anyway, here is a way in which you can fix the problem.
> > 
> > Add a file called (say /etc/logcheck/violations.ignore.d/rng-tools)
> > which contains the line
> > 
> > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rngd: stats: FIPS 140-2 failures: 0$
> > 
> > According to the logcheck documentation, the directory
> > viloations.ignore.d refers to lines that would match entries in
> > violations.d but nevertheless need to be ignored.
> > 
> > I have created the entry in a way that *only* 0 failures for FIPS tests
> > are matched, you may want to create something more general.
> 
> thanks for reassiging the bug and this above rule, i added to logcheck cvs
> the new oneliner for the new file 'violations.ignore.d/logcheck-rgnd':
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ rngd: stats: FIPS 140-2 failures: [0-9]$

Well, if there is a need to keep the "violations.d" stuff overriding the
usual ignore.d, I could add the violatations.ignore.d line myself to the
rng-tools package, but I feel like this is a run-around-my-own-tail problem,
since I have already ignored these log lines in the proper place, and I will
have to add the violations.ignore regexps without knowing WHAT the
violations are (in which case, I will simply duplicate the ignore.d file
into the violations.d.ignore dir).

This really looks to me like a workaround asking for trouble. Is there a
real good reason to have violations override the ignore.d regexps?  If so,
is there a damn real good reason to have anything in the violation regexps
(as opposed as letting the local admin add them)?

I mean, I should not have to add such an ugly thing into a package, in order
to get logcheck to behave (by _default_).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh





More information about the Logcheck-devel mailing list