On 09/19/2016 08:12 PM, Richard Brown wrote:
On 19 September 2016 at 10:43, sdm
wrote: 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.
/var/log/journal exists on my TW boxes
And is persistant storage on my system
My question for the OP though is on what kind of system is a 2GB log a problem?
Why is the journal being blamed? a 2GB /var/log/messages or any other 2GB file in /var/log would have the same negative impact
At least journald can be configured to autoclean upafter itself, or manually cleaned using the journalctl --vacuum-size or --vacuum-time commands
The title of this thread could just as easily be "my root filesystem is too small"
Yes, that is a good point. My root file system is only 20GB, and I have been thinking about making it bigger. I need to take some time to do that, and will have to partition some other drives differently than I currently have them partitioned. However, as Carlos was saying earlier, having it that big apparently ends up using quite a bit of RAM un-necessarily. I have always been told that 20GB should be plenty big for a root file system. It seems that the journal was the main component. I set the limit to 300M, quite a bit bigger than the example recommends, and it gave me enough room to run my kernel update. The confusing thing now is that my journal file is quite a bit smaller - it says 345M at the moment - but when I made that change and rebooted, I cleared about a total of 4GB of use off my root system. Before I limited the size, when I ran du -d -1 -h -x on the root system, it had a total of 19G used. Now it has a total of 15G used. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | Plasma 5.4.7, Qt 5.7.0 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org