It would be great if we also can manage to switch from C to C.utf-8 locales in stdenv and our glibc package as many applications now expect unicode locales (i.e. python). Debian and Fedora are already on board with this. Also since systemd has now support for that too
I’d like to create logrotate rules by default for enabled services like apache, etc… like other distros do, or at bare minimum document the need to rotate logs.
Users coming from Debian can be surprised to find out their logs continue to grow indefinitely instead of being rotated automatically like they are on Debian.
I’m willing to do the work on this, but would like to hear any opinions that people have before I start.
Yeah for desktop use case there isn’t anything to turn on for logrotate usually, as it is covered by journald as you mentioned.
I’m thinking for people who enable services which are not covered by journald.
The 2 use cases I have in mind are apache and rsyslog. I think there is value in automatically rotating those logs for users, like Debian does, or at least making mention in the documentation that the user needs to set up log rotation as most users would expect this to already be in place.
We have a milestone for 19.03 to track issues features and fixes we want included in 19.03. You can see a list of them on GitHub under the 19.03 milestone:
These are sometimes more manageable to try to help out on compared to random ones from the global issue tracker.