On 09/18/2016 03:27 PM, Carlos E. R. wrote:
Yes, you should.
Set limits. For example:
SystemMaxUse=100M RuntimeMaxUse=30M
On my TW box when looking in journald.conf, #Storage=auto is commented out by default like so. From the journald.conf man page: | Storage=| Controls where to store journal data. One of "|volatile|", "|persistent|", "|auto|" and "|none|". If "|volatile|", journal log data will be stored only in memory, i.e. below the |/run/log/journal| hierarchy (which is created if needed). If "|persistent|", data will be stored preferably on disk, i.e. below the |/var/log/journal| hierarchy (which is created if needed), with a fallback to |/run/log/journal| (which is created if needed), during early boot and if the disk is not writable. "|auto|" is similar to "|persistent|" but the directory |/var/log/journal| is not created if needed, so that its existence controls where log data goes. "|none|" turns off all storage, all log data received will be dropped. Forwarding to other targets, such as the console, the kernel log buffer, or a syslog socket will still work however. Defaults to "|auto|". Since by default it's set to "auto" yet that is commented out, it looks like the logs are going into /run/log/journal which is the fallback directory for "persistent" as /var/log/journal doesn't exist on my TW box. So the default setting for TW appears to be volatile, meaning the logs disappear if you reboot the system. Is this correct? Leap was the same way last I checked, so if a user is having their journal file baloon in size the must have at one point changed the defaults in journald.conf (I'm guessing). I don't know if 13.1 and 13.2 have the same defaults for the journal as 42.1 & TW. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org