On Mon 23 Mar 2020 at 19:16:33 (+0000), Joe wrote: > On Mon, 23 Mar 2020 13:15:13 -0400 Greg Wooledge <wool...@eeg.ccf.org> wrote:
> > 5) It does not write logs in human-readable files. You need systemd's > > tools to read systemd's logs. This makes post mortem diagnostics > > much more difficult. > > You might add 5a): Why? > > There's not exactly a burning need to compress text into illegibility to > save disc space these days. How many rational purposes are there to > make logs readable only through systemd's own code? All my buster systems log in the usual manner. Yes, I have some incantations that I've copied from this list, but I don't normally use them. eg: $ journalctl -xe _SYSTEMD_UNIT=ssh.service | lessx -- Logs begin at Mon 2020-03-23 08:11:58 CDT, end at Mon 2020-03-23 21:10:01 CDT. -- Mar 23 08:12:35 wren sshd[701]: Server listening on 0.0.0.0 port 22. Mar 23 08:12:35 wren sshd[701]: Server listening on :: port 22. $ grep 'Server listening' /var/log/auth.log Mar 22 08:10:57 wren sshd[976]: Server listening on 0.0.0.0 port 22. Mar 22 08:10:57 wren sshd[976]: Server listening on :: port 22. Mar 23 08:12:35 wren sshd[701]: Server listening on 0.0.0.0 port 22. Mar 23 08:12:35 wren sshd[701]: Server listening on :: port 22. $ Looks the same to me. Cheers, David.