On 09/19/2016 12:54 PM, Chris Murphy wrote:
On Mon, Sep 19, 2016 at 1:47 PM, sdm
wrote: On 09/19/2016 08:44 AM, Linda Walsh wrote:
From the docs George quoted, the journal should already be set to autotrim -- where it should auto clean itself when the disk is getting near full. It sorta sounds like it didn't do that intelligently -- i.e. he was having disk-full conditions and the log wasn't autotrimming.
The defaults are volatile logs on a clean 42.1 Leap install, because "auto" is should be commented out (can someone verify, on a clean 42.1 install?) and the storage limits commented out by default, which make the journal behave practically like "volatile" as I wrote in the above email. So, George, did you do an upgrade from 13.1 or 13.2? All systemd configuration files show the defaults commented out, including /etc/systemd/journald.conf.
# Entries in this file show the compile time defaults.
So if you have an entry: #Storage=auto
That means it looks for /var/log/journal. If it exists already, then the journal will be stored persistently in that location. If it doesn't exist, it will be stored in /run/log/journal/ which is volatile.
Not on Leap 422. *If* /var/log/journal exists, those journal files are wiped with each reboot, and Leap 42.1 behaved the same exact way for me, although I don't rememember right now if /var/log/journal existed on my past Leap 42.1 box. I wouldn't be surprised if after installing Leap 42.1, and the /var/log/journal directory existed, the behaviour would be exactly the same as Leap 422. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org