there’s also a small amount of disunity in tool vs documentation.
For example, right this moment I happen to be looking for the systemd journal on disk, and man systemd-journal says it lives in /run/log/journal/machine-id. That doesn’t exist. Then you have to embark on a spelunking expedition just to find logging artifacts that have for all (most?) of UNIX history in a standardized logging location, but systemd maintainers have decided on another location and also have decided it’s not where the documentation says it is. So, let’s do the next best thing and look at config files. /etc/systemd/journald.conf manages these sorts of things…Every option commented.
Turns out it’s in /var/log/journal/machineid contrary to the docs or any observable config file (unless some other decision has been made to move it without updating documentation).
I guess moreso just whining because I just wasted time that could’ve been spent more efficiently when (ironically) it was where I would like to see it in the first place, but the tool’s own documentation doesn’t reflect this (Ubuntu 24.04). It’s not a common need, so an “edge case” if you will, but still annoying nonetheless.
It’s little (admittedly) nitpicky issues like this in implementation that raise the ire of old greybeards such as myself. mea culpa, I guess. Not to say older tools were good, perfect, or better, just familiar and well-worn.