On Thursday 03 March 2016, Carlos E. R. wrote:
Telcontar:~ # systemctl status systemd-journald.service systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Active: active (running) since Thu 2016-03-03 12:25:33 CET; 2s ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 26422 (systemd-journal) Status: "Processing requests..." CGroup: /system.slice/systemd-journald.service └─26422 /usr/lib/systemd/systemd-journald
Mar 03 12:25:33 Telcontar systemd-journal[26422]: Runtime journal is using 305.5M (max 400.0M, leaving 600.1M of free 3.6G, current limit 400.0M). Mar 03 12:25:33 Telcontar systemd-journal[26422]: Runtime journal is using 305.5M (max 400.0M, leaving 600.1M of free 3.6G, current limit 400.0M). Mar 03 12:25:33 Telcontar systemd-journal[26422]: Journal started Mar 03 12:25:33 Telcontar systemd-journal[26422]: Runtime journal is using 305.5M (max 400.0M, leaving 600.1M of free 3.6G, current limit 400.0M). Telcontar:~ #
Where is it taking that max size of 400M?
10% or 15% of free memory or the size of /run?
It is ignoring the config, using the default of 10% free ram instead.
man journald.conf: "If the file system is nearly full and either SystemKeepFree= or RuntimeKeepFree= is violated when systemd-journald is started, the value will be raised to percentage that is actually free." Maybe it needs journalctl --vacuum-time=2d or journalctl --vacuum-size=500M cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org