I like some parts systemd does but binary format is travesty. And I do not mean "the fact it is binary is bad" but format itself. Example: strace systemctl

I like some parts systemd does but binary format is travesty. And I do not mean "the fact it is binary is bad" but format itself. Example: strace systemctl status haproxy 2>&1 |grep /var/log/journal |wc -l 356 356 files opened (whole logging dir is around 800MB) only to tell me CGroup: /system.slice/haproxy.service ├─2428 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock └─2434 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock Warning: journal has been rotated since unit was started, output may be incomplete. Yes, to tell me there are no logs for the app. And it takes multiple seconds (I tested it on NAS with spinning rust). because it opens ALL of the logfiles % /var/log/journal1 find . |wc -l 356 The bug has 6 years https://github.com/systemd/systemd/issues/2460 https://github.com/systemd/systemd/issues/2460 If it was just "a SQLite database on some sensible rotation" + maybe pointer-per-app showing where app last logged I'd actually be thrilled. Whole system logs instantly queryable by SQL queries ? Sign me in! Hell, while we're at it slap structured logging there (say if app opts in for it). But this abomination is an utter waste of time.