[CLUE-Tech] Cleaning /var when it gets too full

[bof]

Thanx to all you who wrote.

I've delete the dbbackup package and the backups and gained about 60 MB 
back.

In regards to the sizing of /var, this was the first time that I've been 
bitten by this problem.  I've found, over two years of using Slackware 
and RH and KRUD, that 125 MB was adequate for my system, which is a 
standalone workstation.  I do rotate log files, and tend to delete 
whatever I don't want to keep fairly rigorously. I don't think I need to 
go to partitions for the subdirectories of /var (/var/tmp, /var/spool/, 
/var/log, etc), but it might be useful and I will keep the technique in 
mind.

Still, in the days. of 40 GB HDs, I suppose that it might not hurt to 
allocate more space next time I redo the HD, or when KRUD 8.0 comes out, 
use the resizer to pull some space off another partition and maybe make 
it as big as 126 MB, or even somewhat larger. <g>

In regards to the other comments on partitioning, I've found from 
experience that the following scheme works for me:

    Partition              Size (MB)
    /                        2500
    /boot                      50 (only because RH insists on 40 MB, 
otherwise 20 is enough for Slackware)
    /tmp                      192 (usually 1/2 - 1x size of RAM)
    /var                      128                
    /usr/local               1000
    /home                    whatever is left over
    /swap                    1 - 2x RAM size

These sizes are entirely arbitrary, and will depend upon the size of the 
HD that I have available. If I am installing on a 3 GB drive, then I may 
forgo the above and use only swap and / partitions. I put additional 
software (e.g., portsentry, Netscape, Glimmer, Compupic, OpenOffice, 
etc.) into /usr/local whenever possible. This allows me to retain it and 
my personal data when doing an upgrade or new installation by not 
formatting /usr/local and /home.

BOF