This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new!

Use tmpfs but check init scripts

Posted by: Anonymous [ip:] on July 17, 2008 11:04 PM
Logs feel to me (sysadmin) like an archaic holdover from server days. Desktops do not need them, and certainly not laptops (servers, yes). Linux hasn't graduated yet from a server OS mentality. Ubuntu is trying and some other distros, but all keep logs.

For my users, I put the logs in tmpfs (via fstab) and just let them disappear on shutdown. I am a sysadmin and even I don't see a rationale for keeping them. Yah, I've heard all the arguments about debugging etc. When you crash, or power fails, the last thing you want is disk activity. That spells file system corruption. There is also the OS performance issue. File writes being the major choke point. Why do you want to do that for every little daemon activity?

For us tmpfs works fine. We do use logs, and look at them in tmpfs, and that works fine.

The only minor thing: check any braindead init scripts in case they fail not finding their log folder. You'll have to mod them to create it if not found. This is really a "bug" that upstream should fix. Actually I just have a small pre-script that runs beforehand. It makes the folders in tmpfs at bootup to cover for the braindead scripts.


Return to Improve system performance by moving your log files to RAM