Article 4ZGMN journald setting RuntimeMaxFileSize seems to be ineffective

journald setting RuntimeMaxFileSize seems to be ineffective

by
berndbausch
from LinuxQuestions.org on (#4ZGMN)
I am trying this on Centos 8. From the journald.conf man page:
Quote:
The options prefixed with "Runtime" apply to the journal files when stored on a volatile in-memory file system, more specifically /run/log/journal.
...
SystemMaxFileSize= and RuntimeMaxFileSize= control how large individual journal files may grow at most.
However, RuntimeMaxFileSize seems to be ignored. I specify 4M, the file is 8M. Yes, I restarted the service and even rebooted.
Code:# grep RuntimeMax /etc/systemd/journald.conf
#RuntimeMaxUse=
RuntimeMaxFileSize=4M
#RuntimeMaxFiles=100
# journalctl -u systemd-journald --no-pager
-- Logs begin at Tue 2020-02-18 14:07:13 JST, end at Tue 2020-02-18 14:08:53 JST. --
Feb 18 14:07:13 centos8.home systemd-journald[183]: Journal started
Feb 18 14:07:13 centos8.home systemd-journald[183]: Runtime journal (/run/log/journal/fffced87c0ae4ec2ae3a4c4cb164bda8) is 8.0M, max 91.4M, 83.4M free.
# ls -hsl /run/log/journal/fffced87c0ae4ec2ae3a4c4cb164bda8/
total 8.0M
8.0M -rw-r-----+ 1 root systemd-journal 8.0M Feb 18 14:17 system.journalHas anybody tried to use RuntimeMaxFileSize?latest?d=yIl2AUoC8zA latest?i=bPJ9QLsaPwA:-GyE3vYIeSg:F7zBnMy latest?i=bPJ9QLsaPwA:-GyE3vYIeSg:V_sGLiP latest?d=qj6IDK7rITs latest?i=bPJ9QLsaPwA:-GyE3vYIeSg:gIN9vFwbPJ9QLsaPwA
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments