Carlos E. R. wrote:
Can anyone help? Should I just go into the journald.conf and adjust the parameter to limit the file size? Or is there something else I need to do?
Yes, you should.
Set limits. For example:
From what sdm posted, 'auto' is commented out in the config to note
According to what he posted in the man page, the default should be auto. that auto is the default in the software without any comments being active. I.e. look at the large squid.conf sometime. All of the options are in the conf, but none are commented in as they are simply documenting the default that is built into the software.
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.
Carlos, if what you meant by:
SystemMaxUse=100M RuntimeMaxUse=30M
was that going with the default, e.g.- to only trim when disk space was running out on the log device, was giving it too much space, then I'd agree. Remember though, that the original journal design was designed on a SSD where letting the disk fill, then cleaning it off "shouldn't" hurt future access times. Seems like "auto" is deceptive, since it sounds like it should take care of itself. However, taking care of itself is using all available space until it *needs* to trim. Irk. Given that behavior, maybe suse should provide some other intelligent default (and no -- memory isn't intelligent, it just vaporizes each boot -- and if you are having boot problems, killing off all previous logs each boot isn't very helpful, no? -l -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org