Le Fri, Aug 08, 2025 at 08:03:26PM +0100, Richard Lewis a écrit : > I think this comes back to the scope being not quite explained yet: If > your aim is to have documentation of logging in general then ignoring > the default logger in debian seems unlikely to produce something very > enlightening. Probably you actualy have something else in mind where > this wont actually be an issue.
The scope is described in the wiki article: documenting logging daemons and providing discussion spaces for people with an interest in logging daemons. Including, but not limited to, package maintainers. That systemd-journald is excluded should probably made explicit, I guess I understand why some would expect to see it handled by our team. > Anyway, im happy to help proof-reading or other things -- especially for > logcheck. what are the next steps? You can find them in the wiki article too: https://wiki.debian.org/Teams/Logging#Get_involved For convenience, I’m copying this list of first tasks here: - A first, almost trivial, task would be to write a list of all logging daemons already packaged in Debian. - Logging daemons are supposed to Provides/Conflicts system-log-daemon, in order not to cause breakage when local admin tries to install two of them. Do all implementations we ship actually have this in d/control? Investigate, and report bugs/patches where applicable. - The default logging behaviour of all packaged daemons should be documented. - If there are major differences between the default settings of some daemons, we should probably propose patches to their maintainers to ensure all use a similar baseline on a default setup. - Current focus is on documenting the state of logging daemons in Debian. No packaging skills are required. As you can see, logging-adjacent tools like logcheck are not part of that list yet. Mostly because no people in the team have shown strong interest in them yet, nor have people with interest in them proposed to join the team. But as I wrote earlier, I plan on writing some documentation about logrorate. Hopefully it’s going to spark some motivation for some to come and document other logging-adjacent tools like logcheck. Let’s keep in mind that this is not a definitive list of tasks. It’s growing and changing based on suggestions we get, and is mostly driven by the actual motivations of team members.
signature.asc
Description: PGP signature
