Summary: | sys-apps/logwatch doesn't analyze all logs generated by "hardened" syslog-ng | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Felix Tiede <info> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Team <hardened> |
Status: | RESOLVED NEEDINFO | ||
Severity: | enhancement | CC: | base-system, rajiv |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch to logwatch-6.0.2 config, using "hardened" syslog-ng's log-files |
Description
Felix Tiede
2005-05-19 12:54:20 UTC
Created attachment 59318 [details, diff]
Patch to logwatch-6.0.2 config, using "hardened" syslog-ng's log-files
This is the patch which gets my installation of logwatch-6.0.2 to work with my
installation of "hardened" syslog-ng-1.6.7.
Since logwatch is not very well documented (or I simply didn't find the
documentation) someone should take a look at it and correct it, before using.
Especially the part about daemon.conf and kern.conf is based on guessing.
I've never used this program but I've got a question about /etc/log.d/conf/logfiles/kern.conf do you really need to filter talkd and a few of these other ones? only stuff that should be in kern.log is whatever goes dmesg 3 That's why I said it's based on guessing - I've copied message.conf, changed what I thought was necessary to change and left everything else untouched. can we close this one because there is no more logwatch-6.x in-tree? this is still an issue with logwatch 7.x. (In reply to comment #5) > this is still an issue with logwatch 7.x. > If this is still an issue speak up so we can prioritize bugs to get them resolved. If not please close or request bug be closed. i dont use hardened anymore. |