this post was submitted on 30 Apr 2024
76 points (91.3% liked)
Linux
5191 readers
174 users here now
A community for everything relating to the linux operating system
Also check out [email protected]
Original icon base courtesy of [email protected] and The GIMP
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is journald still binary? That alone made me turn away. I am using PCLinuxOS hence am systemd free. Stopped reading up on it.
Yes, unreadable with a text editor. Meaning that if you have a computer problem and journald or systemd is broken you have can't consult the log files, unless you did install rsyslog or sometimes before that. Meanwhile by default journald will eat a few GBs of disk space soon.
Compared to this what is the advantage of binary form? I thought log files being text was a no brainer.
Storage efficiency, faster queries, more metadata, unified format, etc. If your host breaks, you can download the journals and open then elsewhere. Also, there is nothing stopping you from configuring it to output to a file.
Open them elsewhere is also true for text files I guess.
"on nooo i'm gonna stop using what make modern linux OS good just because they save logs in binary, istead of binary w ith .txt 😭😭" go ahead them, make your life worse
😒
One can keep on using systemd and complain about journald and install rsyslogd and then you'd have the
journalctl -fcommand to impress your Linux noob friends ;-) and /var/log/syslog when there's trouble when journald would be dead.if you can't access journald you have a bigger problem than crying about it's binary file format, but ok keep needing to parse every fucking log using grep and taking 30 second to find anything meaningful if you hate yourself that much