re: for making /var bigger
One method I like to use when running short on space, and cleaning up
crud that I feel I don't need doesn't help, is to buy another hard
drive, decide how much space I'll probably need for say /var/log. Then I
simply move everything from /var/log into the /mnt/newdrive, edit fstab
to indicate that the new partition gets mounted onto /var/log and tada.
More drive space. I used to do the symlink thing, but that often lead to
spaghetti symlinks, becoming more of a headache to manage than the lack
of space was.
Anyway, that's just my 2c.
Sean
On Sun, 2003-01-26 at 02:34, Alvin Oga wrote:
> hi ya
>
> -- i deleted that orig email and decided to reply anyway..
>
> if /var is too full... you can also do the following:
>
> - ls -la /var/spool/mqueue /var/spool/mail /var/spool/clientmqueue
> - remove any junk ...
> - mailq should tell you of any pending emails
>
> - ls -la /var/log
> - how big are your log files ...
> - is it rotating foo.1, foo.2, foo.3 ...
>
> if you have a growing web tree under /var/www
> i'd move that to /home/www instead
>
> if i rememer correctly.. you had /usr/local ( basically unsused )
> and /usr ....
> i'd move /usr/local/* back into the /usr tree
> and convert /var into /usr/local
> ( but i forgot how big your /usr/local /var was )
>
> moving things that grow like /var/log and /var/spool out of
> /var will also prevent /var from getting full
>
> -- no matter how big your partitions are...you will always
> run out of space at the wrong time
> ( typically when you dont have the time to deal with it )
>
> c ya
> alvin
>
Reply to: