On 2018-05-22 16:14, Patrick Shanahan wrote:
* Per Jessen <> [05-22-18 09:24]:
[...]
I did test it before I wrote my reply, if you stop journald, rsyslog and syslog-ng both stop logging.
Anyway, if you don't want journald writing to disk, but you still want syslog working, use "storage=volatile" and "forwardtosyslog=yes" in /etc/systemd/journald.conf
I accomplish nearly the same by setting SystemMaxUse=5 and ForwardToSyslog=yes
Still, entries are written to both places, that's some i/o load. On my main machine I limit its disk space load, with the result that now the boot entries have been purged out (no permanent journal). On my server machine I left it on with ample space, for testing what would happen: cer@Isengard:~> journalctl --disk-usage Archived and active journals take up 2.0G on disk. cer@Isengard:~> The syslog files use 269 MB, much less and probably several months more of logs. Journal start: -- Logs begin at Sun 2017-08-20 17:50:07 CEST, end at Tue 2018-05-22 17:11:16 CEST. -- Aug 20 17:50:06 Isengard systemd-coredump[8943]: Process 17740 (Kodi_MovistarTV) of user 1000 dumped core. Syslog start: <5.6> 2017-01-22T21:29:18.565260+01:00 Isengard rsyslogd - - - message repeated 143 times: [-- MARK --] -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))