[lug] Cleaning up /var when it gets too full
gsexton at mhsoftware.com
Mon Sep 16 11:24:17 MDT 2002
It would be worth at least looking at what's stored in lib.
From: lug-admin at lug.boulder.co.us [mailto:lug-admin at lug.boulder.co.us]On
Behalf Of bof
Sent: 16 September, 2002 9:12 AM
To: lug at lug.boulder.co.us
Subject: Re: [lug] Cleaning up /var when it gets too full
Sexton, George wrote:
>It would be helpful if you did
>du -s *
>from the /var directory so you could see where your space is going.
Here's the listing of /var using du -sh *
It would appear that the lib directory is taking up most of the space.
So using du -sh * against lib, I find
So most of the space is taken up by rpmrebuilddb and the dbbackup
directory, the contents of which are
From the above, I gather that I can delete the first three rpm files,
and the rpmrepbuilddb.18035 file to regain almost 60 Mb of space.
I don't use mason, so I've uninstalled it.
Is there anything else I could delete safely?
And what about regaining space automatically? I do use logrotate for
keep my log files, but is there anything else I could be doing?
Web Page: http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
More information about the LUG