News for hackers. Stuff that matters.
Re:Without Systemd by gaius_baltar on Friday July 28, 2017 @03:43PM (#14876927)
Maybe I'm stepping into a hornets nest by commenting this but after some initial estrangement, I now absolutely love having systemd in the servers I manage. Thanks for providing me with an easy and sane way to manage processes, pretty simple one to configure control groups and other restricted execution environments, monitoring, etc.

That made me see how much time I wasted writing non-trivial init scripts and reworking with the trivial ones. I simply don't want to get back now.

Re:Without Systemd by sekh60 on Friday July 28, 2017 @03:56PM (#14877033)
I have always been a fan of most of systemd. The only complaint I really have is the binary file logging. I feel that should be plain text.
Re:Without Systemd by db48x on Friday July 28, 2017 @06:32PM (#14878107)
I think it would still have to be some kind of structured format (one json object per "line", for instance), so that it could keep all of the metadata. On the other hand, you can use journalctl --output=json to get exactly that, so...
Re:Without Systemd by kpcyrd on Saturday July 29, 2017 @12:37PM (#14881954)
I have a grief with plain text logs. They are really nice if you want to read them manually with vim or less, but are super painful if you want to parse them automatically.

It doesn't help much that a fair number of logging libraries have buggy formatting to an extend that you can't safely parse plain text log files sometimes.

For example this bug (mostly fixed by now) https://github.com/sirupsen/logrus/issues/531