On 12/11/25 3:20 PM, Nicolas George wrote:
Paul M. Foster (HE12025-12-11):Systemd has a lot of parts, most of which most distributions don't use. One annoyance of systemd is that it effectively encrypts the system log. You have to use something like journalctl to get at the logs, rather than just feeding them to less or more.Are you complaining that you need a command provided by a binary in your path to read these logs instead of another command provided by another binary in your path?So, is it possible to get regular unencrypted system logs on systemd?The answer depends on your exact definition of “on systemd”. Regards,
On systems which don't use systemd, the log files are in clear text, and you can simply use cat or more or less and/or grep to read through the files. This isn't true for systemd systems. Instead, the log file(s) are more or less binary. I don't like that. Thus, I am looking for a way to have clear text log files while still running systemd (since I really can't avoid systemd on Debian).
Paul
--
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster
https://codeberg.org/paulmfoster
https://github.com/paulmfoster