News for hackers. Stuff that matters.
Re:Avoiding Complexity with Systemd by sseagull on Sunday June 27, 2021 @11:03AM (#27652117)
I think the argument is really about transferablilty of skills. I already know how to manipulate compressed files because I have to do that in other places. And once you realize logs are just text files, I can immediately transfer all my skills of dealing with text files to dealing with logs.

But now I have to learn another set of tools (or at least another command to convert it to text files). It's not really a huge issue (I'm not really a systemd hater), but there can be a bit of dread when all the tools move off of standard formats, like simple text files, to custom formats, requiring you to learn idiosyncrasies of lots of different packages.

(And the reverse is true. Knowing how to use journalctl only helps me with systemd, and nowhere else. It's a piece of knowledge helpful in only one area that I cannot transfer anywhere else)

Re:Avoiding Complexity with Systemd by cout on Sunday June 27, 2021 @01:56PM (#27653658)
I think this is exactly it. Journalctl doesn't resemble any tools I already know, so I have to look up how to use it each time. Binary logs aren't the problem; we have had those for ages (e.g lastlog). I just wish journalctl were a little more familiar.
Re:Avoiding Complexity with Systemd by shawnz on Sunday June 27, 2021 @07:12PM (#27656352)
> Journalctl doesn't resemble any tools I already know

What about "tail"?

Re:Avoiding Complexity with Systemd by lanstin on Sunday June 27, 2021 @01:45PM (#27653550)
I think you can pump all the journal log files to a text file and then open them in emacs and start writing Python to analyze ;)