also sprach Hanspeter Kunz <[EMAIL PROTECTED]> [2007.09.20.1415 +0100]:
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ acpid: received event
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ acpid: notifying client
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ acpid: executing action
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ acpid: action exited with status 0$
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ acpid: completed event
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ acpid: client connected from
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ acpid: [0-9]+ client rule.* loaded$
>
> They ignore pretty everything, unless there is an error.
>
> The first line ignores all kind events (battery, lid, power, hkey). Or
> are there acpi event that should trigger logcheck?Thanks! In general, I don't think logcheck should let any acpid messages pass, so this should be okay. I am missing information about where these filters go, but I'll assume ignore.d.server/acpid. Also, you might want to have a look at http://wiki.logcheck.org/index.cgi/RuleSubmission for future submissions. Specifically, we don't really want rules that don't cover the whole line and do not end with $. And in between, the filter should be as specific as possible. Do you want to try to fix the rules up? If not, then please send me the log messages that weren't filtered and I'll update them. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
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
