[systemd-devel] Journal file is synced each minute into disk
Ricardo Fraile
rfraile at idealista.com
Mon May 9 15:21:03 UTC 2016
Hello,
With the following configuration in "/etc/systemd/journald.conf":
[Journal]
Seal=no
SplitMode=none
SyncIntervalSec=5m
RateLimitInterval=0
RateLimitBurst=0
ForwardToSyslog=no
SystemMaxUse=5G
SystemKeepFree=500M
RuntimeMaxUse=500M
RuntimeKeepFree=250M
The file "system.journal" located under "/var/log/journal/[number]/" is
synced each minute, for example:
# ls -al
-rw-r----- 1 root root 8388608 May 9 17:05 system.journal
# ls -al
-rw-r----- 1 root root 8388608 May 9 17:06 system.journal
But its extrange since the variable "SyncIntervalSec" have the "5m"
value and the man page said:
SyncIntervalSec=
The timeout before synchronizing journal files to disk. After syncing,
journal files are placed in the OFFLINE state. Note that syncing is
unconditionally done immediately after a log message of priority CRIT,
ALERT or EMERG has been logged. This setting hence applies only to
messages of the levels ERR, WARNING, NOTICE, INFO, DEBUG. The default
timeout is 5 minutes.
Ok, maybe any important error is generated, but is not the case, the
journal didn't report anything:
# journalctl -p crit -p alert -p emerg
-- Logs begin at Mon 2016-05-09 15:51:12 CEST, end at Mon 2016-05-09
17:12:54 CEST. --
Is this the right behaviour?
How is possible to delay the sync of the persistent journal file?
# systemd --version
systemd 215
+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
-SECCOMP -APPARMOR
...runing in Debian Jessie 8.4
Thanks,
More information about the systemd-devel
mailing list