[lug] Cleaning up /var when it gets too full
bof
bof at pcisys.net
Mon Sep 16 08:28:39 MDT 2002
Hello,
How does one go about cleaning their /var partition when it gets full?
When I set up KRUD 7.3, I allocated a partition size of 125 MB for /var.
Now it has some 117 MB in it, so it is almost 100% used, and I can't
print anything because CUPS can't get enough space in the spooler for
its print jobs. Surely I don't need all the stuff on /var, since it
wasn't on the system when I set it up initially --- I thought /var was
for a temporary holding area, so no files on it would be permanently
needed and could be deleted as necessary. But I am not sure what I can
and cannot delete to clear up space on it. I've looked at the file
listings, and it's lots of little files and directories, no one of which
is too big by itself, and many which are empty, but all of which add up
when taken together.
The top level listing of /var is:
analog-5.24
cache
db
empty
lib
local
lock
log
lost+found
mail
nis
omninames
opt
preserve
run
spool
tmp
www
yp
So what can I keep and what can I delete, and what would be the best way
to go about doing this --- is there a way of setting a cron job to
delete uneeded files?
Thanx.
BOF
More information about the LUG
mailing list