* Andreas Tille in "[OT] logcheck and fetchnews" dated 2000/08/21 14:05 * wrote: > Hello, > > sorry for posting this to devel but I failed while asking other > lists. I just want to make sure that it is a bug of logcheck and not > my own before I file a bug-report: ...snip... > Seems strange why I did define some rules which are stronger than > others but they are just all my trials which failed to block the > following messages. I hoped that the first rule should have deleted > all fetchnews entries but I continueally get the follwoing type of > messages: > Security Violations > =-=-=-=-=-=-=-=-=-= > Aug 21 11:03:39 wr-linux02 fetchnews[19687]: illegal article: /var/spool/news/interbase/public/general/1096: Illegal seek > Aug 21 11:03:39 wr-linux02 fetchnews[19687]: illegal article: /var/spool/news/interbase/public/general/1097: Illegal seek > Aug 21 11:03:39 wr-linux02 fetchnews[19687]: illegal article: /var/spool/news/interbase/public/kinobi/jdbc-odbc-oledb/54: Illegal seek > Aug 21 11:03:39 wr-linux02 fetchnews[19687]: illegal article: /var/spool/news/mers/interbase/list/1147: Illegal seek > .... > > Could anybody help me out of this boring messages? > Is this a bug of logcheck? No, just someone who didn't read the documentation. You need to create lines to ignore violations in logcheck.violations.ignore, if you'd read the documentation in /usr/share/doc/logcheck though you'd know that. Check INSTALL.gz and it clearly defines the purpose of each of the files in the /etc/logcheck hierarchy. -- shaky cellar
Attachment:
pgpEkVWByECVk.pgp
Description: PGP signature