On Tue, Dec 03, 2024 at 10:00:27 +0700, Max Nikulin wrote: > <https://0pointer.de/blog/projects/systemctl-journal.html> > systemd for Administrators, Part XIII > Posted on Fr 18 Mai 2012 > Log and Service Status > > > The original reason we started to work on the journal was one specific > > feature idea, that to the outsider might appear simple but without the > > journal is difficult and inefficient to implement: along with the output > > of systemctl status we wanted to show the last 10 log messages of the > > daemon. > > I could not recall where I saw a more verbose description of design ideas. > Perhaps faster selection of records within a given time range. > > Journald&journalctl have their shortcomings, but often they are more > convenient during debugging: more precise timestamps, filtering by all > processes from a service cgroup.
Separate logs per service aren't a new idea. Service managers that came before systemd (e.g. daemontools) were doing that already. And you don't need *binary* files to achieve it. However, my comment wasn't about systemd's design choices. It was about Debian's choices. > On 30/11/2024 03:29, Greg Wooledge wrote: > > Now, you might ask why the systemd journal is being preferred and kept > > over human-readable log files. I don't think anyone on debian-user > > knows the answer to this. What I don't know, and don't think anyone on this list knows, is why *Debian* chose to toss the human-readable separate text log files away in favor of the systemd monolithic binary journal. Anyway, this is all academic at this point. We know what Debian chose, and we know how to make our own choices, if we want something else.
