On 2016-09-19 14:12, Richard Brown wrote:
On 19 September 2016 at 10:43, sdm <> wrote:
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
But the OP did not say he is using TW. That was 'sdm', another poster.
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?
He must have a small disk, or a small root partition.
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
Well, the journal is blamed because (apparently) he has journal and not syslog ;-) That is the default, anyway.
At least journald can be configured to autoclean upafter itself, or manually cleaned using the journalctl --vacuum-size or --vacuum-time commands
Yes, but you can define size limits and this will happen automatically when needed.
The title of this thread could just as easily be "my root filesystem is too small"
Yep. That too. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)