What if I’m on another minimal distro, like Artix, that doesn’t use systemd? Journald is a systemd thing, and I’m not going to install systemd on top of a perfectly good init system.
If adopt systems then the question is easy to answer: no, journald does everything you need.
without adopting systemd… well. Are you evaluating going without any log handling at all and maybe just dumping logs ephemerally to tty0? DIYing all log stuff like your init scripts DIY things?
Personally if I had to go without journald I’d probably go back to using syslog-ng. But I guess there’s an argument for shipping straight into something like opentelemetry-collector if you’re willing to put in a lot of work.
Check that you actually have persistent storage enabled. (See
man journald.confand search forStorage)Read up on the numerous parameters to journalctl. (
man journalctl)journalctl --boot -2will show logs from previous boot.journalctl --since "-2 weeks" --unit=sshdlast two weeks worth of sshd logs.I think there’s a minor mistake in your command.
jounalctl --boot -1is the previous boot. The counting starts at--boot 0for the current one.You’re right ofcourse.
What if I’m on another minimal distro, like Artix, that doesn’t use systemd? Journald is a systemd thing, and I’m not going to install systemd on top of a perfectly good init system.
If adopt systems then the question is easy to answer: no, journald does everything you need.
without adopting systemd… well. Are you evaluating going without any log handling at all and maybe just dumping logs ephemerally to tty0? DIYing all log stuff like your init scripts DIY things?
Personally if I had to go without journald I’d probably go back to using syslog-ng. But I guess there’s an argument for shipping straight into something like opentelemetry-collector if you’re willing to put in a lot of work.
On distros w/o systemd there is always syslog-ng. s6 also has its own log system.