Hi, couldn't logcheck get much more clever on a systemd-enabled system? After all, the priorities are preserved, so everything of priority "info" or lower could be ignored automatically - and only warnings and errors considered further. Actually that's one of the reasons why I am looking forward to running systemd on my servers.
Kind regards Ralf On 28/08/14 17:22, Russ Allbery wrote: > Ondřej Surý <ond...@sury.org> writes: > >> I have started to collect logcheck/ignore.d.server/systemd rules for >> systemd: > >> https://wiki.debian.org/systemd/logcheck > >> I think it might be a good idea to fine tune the rules before submitting >> them for inclusion into logcheck default ruleset... > > Should we include rules that match lines like: > > Aug 28 07:30:01 lothlorien systemd[1]: Starting Run anacron jobs... > Aug 28 07:30:01 lothlorien systemd[1]: Started Run anacron jobs. > > or should those be in the anacron package / rule set? I could see an > argument either way. > -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54010645.7060...@ralfj.de
