* Carlos E. R. <robin.listas@telefonica.net> [05-22-18 11:15]:
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.
14:02 Crash:~ > journalctl --disk-usage Archived and active journals take up 2.5M in the file system. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org