Software - Support > Other

SystemD log size

(1/1)

trinidad:
This is on LL5 and I did not clear the journal until yesterday. I'm going to monitor it now and see how quickly it builds up again. I suspect some of it was left over from installation, and the fact that I left the system unused for a couple of months thus needing a large update as I mentioned a while back. It may be that not updating regularly increases the journal size when a system is finally updated. I'm sure several usage factors can influence the pace of the journal's growth. It just jumped out at me because this system was barely used, but that may be the actual cause.   

TC     

Jerry:

--- Code: ---/etc/systemd/journald.conf
--- End code ---


--- Code: ---[Journal]
SystemMaxUse=250M
SystemMaxFileSize=50M
--- End code ---

ref. - https://wiki.manjaro.org/index.php/Limit_the_size_of_.log_files_%26_the_journal#How_to_set_a_maximum_size_limit_for_the_journal

This is left unchanged in LL because there may be somewhere in a large log the clue to a problem someone is having. We don't want to eliminate clues.

trinidad:
I think someone posted on this subject once before but I'm looking into it myself now. My systemd log has hit 1.2gig and that would be excessive for users on smaller systems and undoubtedly eventually cause an issue. I suspect that logs are being updated unnecessarily for several applications that are rarely if ever used, but the problem there is that I would have to find some way customize logging according to user preferences. If 1.2gig is the rollover limit for the logs I think it will prove to be to high as some users' systems grow. I once let debsecan run on one of my Debian systems for three years without deleting anything and it didn't even approach that figure even though it reports CVEs back to 2014. Why is this log so big, or configured to be so big? It does not do this in Debian.
TC   

Navigation

[0] Message Index