[lug] Cleaning up /var when it gets too full
Timothy C. Klein
teece at silverklein.net
Mon Sep 23 11:30:29 MDT 2002
* Sean Reifschneider (jafo at tummy.com) wrote:
> On Wed, Sep 18, 2002 at 10:01:22PM -0600, Bear Giles wrote:
> >This may seem like a lot of effort, but experience shows that it
> >eliminates a *lot* of problems. It's a lot like that old commercial
> Unfortunately, on systems without a nice LVM and online resizable
> filesystems, creating a bunch of partitions tends to create a lot more
> problems than it eliminates... Unless you have a really good idea up front
> what the high water mark of /var/tmp, /var/log, /var/spool, etc are, you're
> likely to run out of space in some of them while others have plenty to
> Mostly I'm going with simpler partitioning schemes -- always a /boot up
> front on the disc, then usually either just a / or a / and /home.
I sure agree here. When I first started using Linux a few years ago,
all the advice seemed to point to multiple partitions. I suspect this
was just becuase most Unix folks were used to server machines. If you
want to make sure you log and mail files don't get DOSed and bring down
the system by eating up all disk space, I guess a separate /var is good.
And a /usr/, /usr/local, etc.
For the average home Linux user, though, that is a major pain in the
bleep. It just causes problems. Your needs will inevitably change, and
then you are stuck with an unwieldy system.
== Timothy Klein || teece at silverklein.net ==
== ---------------------------------------- ==
== "Hello, World" 17 Errors, 31 Warnings... ==
More information about the LUG