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.

[–] [email protected] 2 points 6 months ago (1 children)

Compared to this what is the advantage of binary form? I thought log files being text was a no brainer.

[–] [email protected] 7 points 6 months ago (1 children)

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.

[–] [email protected] 2 points 6 months ago

Open them elsewhere is also true for text files I guess.

[–] [email protected] -2 points 6 months ago (1 children)

"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

[–] [email protected] 4 points 6 months ago* (last edited 6 months ago) (1 children)

“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 -f command to impress your Linux noob friends ;-) and /var/log/syslog when there's trouble when journald would be dead.

[–] [email protected] 1 points 6 months ago

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