No how to do that ?
1 Like
logrotate
The logrotate utility is designed to simplify the administration of log files on a system which generates a lot of log files. Logrotate allows for the automatic rotation compression, removal and mailing of log files. Logrotate can be set to handle a log file hourly, daily, weekly, monthly or when the log file gets to a certain size.
systemctl status logrotate
● logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Active: inactive (dead)
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
systemctl enable --now logrotate [3]
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
cat /etc/logrotate.conf [4]
# see "man logrotate" for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
# restrict maximum size of log files
#size 20M
# create new (empty) log files after rotating old ones
create
# uncomment this if you want your log files compressed
#compress
# Logs are moved into directory for rotation
# olddir /var/log/archive
# Ignore pacman saved files
tabooext + .pacorig .pacnew .pacsave
# Arch packages drop log rotation information into this directory
include /etc/logrotate.d
/var/log/wtmp {
monthly
create 0664 root utmp
minsize 1M
rotate 1
}
/var/log/btmp {
missingok
monthly
create 0600 root utmp
rotate 1
}
2 Likes
I usually edit journald.conf to limit the system log size.
sudo micro /etc/systemd/journald.conf
See journald.conf(5) for details
Edit journald.conf to something like the following (just a rough template to try):
[Journal]
Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=login
#RateLimitInterval=10s
#RateLimitBurst=200
SystemMaxUse=500M
SystemMaxFileSize=250M
MaxRetentionSec=14 day
MaxFileSec=3 week
ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
Play with the settings to see what you like.
You may also want to disable the core dump logging in /var/lib/systemd/coredump/. If you have a program crashing regularly the logs can grow to a massive size. You can always re-enable it later if you require the logs for debugging purposes.
I'm not claiming to be an expert with the configuration settings, so I'd experiment with them to find a balance you like. I had a problem with kdeconnect creating coredumps a couple years back. I couldn't do without kdeconnect so I just lived with the coredumps and limited the logs sizes until it was fixed.
Obviously YMMV.
Perhaps others can post their methods as well.
The problem with limiting log size by default is some people want their debug logs to go back to the beginning of time. However, it might be an excellent addition to the welcome app to easily apply log limits for those that want it to help save space @librewish .
2 Likes