also sprach Thijs Kinkhorst <[email protected]> [2009.02.11.1539 +0100]: > However, that doesn't work because of course I don't have all the > packages I use on my network installed on my loghost. In fact, > I believe that usually the default is that the loghost doesn't do > (many) other tasks than logging and logcheck, so those per-package > shipped files do never end up on the loghost.
logcheck is not designed for loghosts. > How are these files supposed to end up on the loghost? Or would it > be better if all ignore.d files would be shipped inside the > logcheck-database package? Having all of the in logcheck-database just results in massive piles of unmaintainable regexps, as is the status quo. logcheck-database just exists, because maintainers are lazy and don't do the maintenance themselves, maybe because logcheck isn't considered a standard. It would be nice if it were, but I cannot really vouch for the current implementation (and the ruleset), which is really just a huge pile of dung. So, to answer your question: provide them in the package if possible, or tell me to add you as committer to logcheck-database, add them, and make a release. And then rewrite logcheck properly, or at least implement a way to reuse common patterns in the rulefiles. :) -- .''`. martin f. krafft <[email protected]> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "politics is the entertainment branch of industry." -- frank zappa
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
_______________________________________________ Logcheck-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/logcheck-devel
