Richard Brown wrote:
My question for the OP though is on what kind of system is a 2GB log a problem?
He didn't say it had filled all partitions on his disk. The question you should be asking is what size partition is using up 2GB space a problem. 2GB would be > 25% of my 'var' partion (currently using 2.5G out of 7.8G). So 2GB wouldn't be a problem if it was trimmed. However, if the journal behavior is to fill until full and only trim then, that could be problematic on any file-system. My boot partition is "only" 908M, but then it wasn't designed to hold logfiles.
The title of this thread could just as easily be "my root filesystem is too small"
My logs are set to trim @ 4M, but they are separate logs/function. A log that has grown to 2GB would be indication of abnormal behavior on my system. A 2GB catch-all log would also be a binary-blob, unuseful to monitor day-to-day problems. Right now, my largest log is my lastlog @ 19M, which covers logins going back to aug-24 -- which was when I think I fixed it: lindaw pts/4 athenae Mon Sep 19 07:45 still logged in root tty1 Thu Sep 15 19:54 - 07:45 (3+11:51) ... lindaw pts/0 athenae Fri Aug 26 16:38 - 01:09 (08:31) reboot system boot 4.7.1-Isht-Van Fri Aug 26 16:35 - 22:47 (15+06:11) ... wtmp begins Wed Aug 24 10:57:47 2016 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org