News for hackers. Stuff that matters.
Re:Porting systemd to musl Libc-powered Linux by jauntywundrkind on Thursday September 05, 2024 @10:06AM (#41456771)
First, i'm a vocal systems appreciater. But. The one thing that frustrates me about the journal is that there is only one journal. If I have a chatty app, it can entirely take over the journal. Set a 1GB hour al, come back in a couple days, and nothing else is left in the journal other than it logging. I hate this so much.

If I could assign some apps to a secondary journal, or better quota individual services, that would make sure I can keep tabs on my entire system, even when one app is logging heavily.

Re:Porting systemd to musl Libc-powered Linux by hackernudes on Thursday September 05, 2024 @10:20AM (#41456903)
Check out the LogNamespace option.
Re:Porting systemd to musl Libc-powered Linux by Brian_K_White on Thursday September 05, 2024 @08:33PM (#41461701)
Why? Why must someone check out a new more complicated way to do something that was already simple by default before logs were turned into db rows?
Re:Porting systemd to musl Libc-powered Linux by jauntywundrkind on Thursday September 05, 2024 @11:38PM (#41462681)
Bro no. Logrotate shit was gross and gnarly. Every service has its own way of doing with logs. None of it worked the same. It never was simple it always had been crap.

I have my complaints but not replying on each service to do something special conpatible with each other log rotation system was not a complaint. Having this managed reasonably has been great.