Logcheck devel - Feb 2009 - where to submit new logcheck rules?

Hi,

I've got a few logcheck ignore.d rules that I'd like to submit, one
example is sqlgrey. /usr/share/doc/logcheck/README.maintainer talks
about shipping the rules inside the package itself, so I could file a
request with sqlgrey.

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.

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?


cheers,
Thijs

-- 
Thijs Kinkhorst                                thijs at uvt.nl
LIS Unix                                        kamer G 236

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 544 bytes
Desc: OpenPGP digital signature
Url :
http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20090211/e613dd49/attachment.pgp

also sprach Thijs Kinkhorst <thijs at uvt.nl> [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 <madduck at d.o>      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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
Url :
http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20090211/afe386e7/attachment.pgp