Reliability and transparency? You're kidding, right? Systemd in their infinite wisdom decided that journald can choose when to log and when not to log somethi

Reliability and transparency? You're kidding, right? Systemd in their infinite wisdom decided that journald can choose when to log and when not to log something. Historically, syslog etc have been a very thin barrier between programs and outputting logs. Journald now decides if and as and when it's going to bother putting logging data to disk. One of the things they've decided is you don't really need logs when you run the reboot command. In fact, if you really want logs you have to dig in to their documentation to find this: https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 https://freedesktop.org/wiki/Software/systemd/Debugging/#ind... That tells you to adjust kernel parameters and write a file to disk to explicitly re-enable logging. I lost a whole bunch of time recently troubleshooting something on a server running systemd that was interfering with the reboot process, because systemd logged sweet FA. I had a pretty good idea what the problem was, but lack of logs made it significantly harder to nail down. The actual problem is one I've run into all sorts of times in the past, and in every non-systemd case, there's always been enough detail in the logs from the init system to nail it precisely from the get go.