Hans Witvliet said the following on 04/09/2011 09:52 AM:
In case you run processes that "complain" a lot, you might consider putting /var/log into a separate partition. Some even put /var/run into a tiny seperate partition (some MB) so that they have a garanteed working area to write their PID
Its easy enough (go google) to put /var/run and /var/lock in a tmpfs. Its not that difficult to put /tmp in a tmpfs if you think you can spare the ram/swap. The tmpfs file system is even more of "an elastic band" than LVM! And the nice thing is that it gets purged on reboot! There is a slight speed advantage in not hitting the disk for /var/run and /var/lock, but you'd be hard pressed to see it, not least of all in that if you're that hard pressed you're probably consuming ram and pushing it out onto swap and so getting back the disk activity. But having /tmp as a tmpfs *does* make a difference Years ago, Mike Tilson of HCR wrote a driver for SCO XENIX (if you can remember that far back) which mapped the i-nodes of the V7fs into the high ram on a PDP-11 that the OS itself couldn't make use of :-) Boy! did that make a difference! Later model file systems aren't quite that easy to map and later model Linux makes better use of address space (and if it doesn't, then use -pae), so we end up with tmpfs. Its a winner.And its easy to use. There are fixes out there for mapping /var/log to a tmpfs, but that makes me a bit nervous; I like to be able to retain logs across boots. -- Let us never forget that government is ourselves and not an alien power over us. The ultimate rulers of our democracy are not a President and senators and congressmen and government officials, but the voters of this country.” -- Franklin D. Roosevelt -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org