Ralph
Checked my Logrotate.conf and it's same as yours:-
# see "man logrotate" for details
# global options do not affect preceding include directives
# rotate log files weekly
weekly
# use the adm group by default, since this is the owning group
# of /var/log/.
su root adm
# keep 4 weeks worth of backlogs
rotate 4# create new (empty) log files after rotating old ones
create
# use date as a suffix of the rotated file
#dateext
# uncomment this if you want your log files compressed
#compress
# packages drop log rotation information into this directory
include /etc/logrotate.d
# system-specific logs may also be configured here.
Anything I should change in there?
Clive
On 31/08/2026 14:02, Ralph Corderoy wrote:
Hi Tim H,
When the log files gets to a certain size or a pre-determine time
(weekly, monthly etc) the system will compress them for archiving
hence the .gz files.
This is done by the logrotate program.
Its configuration comes from the /etc/logrotate.conf file,
and the files in the /etc/logrotate.d directory.
Altering its configuration to keep fewer log files, or ones which go
back less time, would have it remove the older ones when it's next
automatically run. And keep on removing them.
For example, my /etc/logrotate.conf includes:
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
But unless ‘sudo du -sh /var/log’ suggests /var/log is a particular
disk hog, then Clive will probably achieve enough space savings with his
kernel clean-up. And that's something which will grow forever
otherwise.
--
*C Wills***
--
Next meeting: Online, Jitsi, Tuesday, 2026-09-01 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... https://dorset.lug.org.uk
New thread, don't hijack: mailto:[email protected]
