Re: Files piling up in /var/* directories
Gene Heskett wrote:
On Saturday 11 March 2006 06:52, Charles wrote:
I've noticed that I have files piling up in /var/cache, /var/log, and
/var/lib. These three folders now have 100 mb of files in them.
Which of these must be present for the machine to run? This is (at
the moment) a home machine; I don't *need* the log files, but I
don't know what happens if I just delete the files in these three
That will eat your lunch. If logrotate is properly setup, those files
will not grow beyond what they are as the old ones will be expunged
With disc space a commodity thing, a 500 meg /var partition is
But if you have only one disc, it is a fungible commodity, and
reclamation is the way to go. I agree with logrotate. I use it,
and my /var looks like this...
# du -s /var/* | sort -gr
I don't think that 5MB is too big for my log files. I *do* wonder
about /var/spool, however. Hmm...
# du -s /var/spool/* | sort -gr
Yep, my package manager's the culprit. And...
# du -s /var/cache/* | sort -gr
Also my package manager.
unimaginable today, my /var/cache alone is 1,273,796 whatevers in du's
default format. Which is not a big deal since /var is on /dev/hdd, a
That's way more than I would permit on my machine. I not only find
it imaginable that /var would be < 500MB, my /var is < 300MB. And
on occasion, I have cleaned out the package manager stuff (though
it tends to come back).
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda5 7633264 6147620 1097896 85% /
/dev/hda3 99075 24602 69358 27% /boot
Not everyone can afford hundreds of Gigs of disc space.
If disc is so cheap, will you buy me a new, larger drive?
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!