5 ms·
What does canonical log even means here? Systemd will produce logs in its own structured representation and write them straight away as plain text in the logge
by WastingMyTime89 4y ago
What does canonical log even means here?
Systemd will produce logs in its own structured representation and write them straight away as plain text in the logger of your choice. For all intent and purpose, you now have text logs.
- denton-scratch 4y agoWhat I meant by "canonical" is that you can't get rid of the binary log; you can pipe it into a database, or a textfile, or /dev/null, if you want, but that database or textfile is transcoded copy of the binary log.
- ecnahc515 4y agoThat's not true, you can configure journald to be in-memory only in which case there's no binary log, no file. If your using systems, you can't really git rid of journald, but you can get rid of the binary logs.
- denton-scratch 4y agoI wasn't aware of that. Can you make the memory usage arbitrarily small?
- WastingMyTime89 4y agoEvery log ever is a transcodification of a system state. What difference does it actually make that it is emitted into systemd structured format before being put into your logger? Seems like a pointless complain to me. It’s arguing for the sake of it.
- denton-scratch 4y agoOh, I didn't complain. I know better than to come to HN and complain about systemd.