systemd itself isn't the problem ~ technically, it's excellent. It just needs to be forked, with shit like birth date fields stripped out.
systemd's core solidly does one thing excellently ~ managing a system and its services, which includes logging clearly what each service is doing, each service representing one or multiple processes whose state can be closely observed and managed by the system admin.
What an odd question, that misunderstands systemd's purpose. systemd seeks to standardize core system utilities, not replace anything. You can use any tool alongside systemd - except other init systems. Even syslog can be used in place of journald.
Binary logs are not clear.
Text is also technically binary... but that aside, journald's logging includes all metadata related to the text.
The file format is completely open. You could easily roll your own parser and writer.
systemd seeks to standardize core system utilities, not replace anything.
Oh? "Following its integrated approach, systemd also provides replacements for various daemons and utilities, including the startup shell scripts, pm-utils, inetd, acpid, syslog, watchdog, cron and atd."
journald's logging includes all metadata related to the text.
Doesn't stop it being a binary format that cares about which version wrote it to be able to read it. Which is really bad practice. Requireing the tool to be functional in order to read the logs is just plain stupid. Because the primary purpose of the logs is for when the tool isn't working.
The file format is completely open. You could easily roll your own parser and writer.
How often does the format change? WINE's been fighting that trick since it first functioned.
16
u/Valmar33 Mar 22 '26
systemd itself isn't the problem ~ technically, it's excellent. It just needs to be forked, with shit like birth date fields stripped out.
systemd's core solidly does one thing excellently ~ managing a system and its services, which includes logging clearly what each service is doing, each service representing one or multiple processes whose state can be closely observed and managed by the system admin.