** Description changed: In Ubuntu, we have always cleared /tmp on every boot. As such, on servers, by default /tmp should actually be a tmpfs entirely in RAM, when there is enough memory in the system. This threshold should be configurable by the end user (in cloud-init?), and default threshold of ~2GB. Read about tmpfs here: https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt This has several advantages, mainly: * Performance - much faster read/write access to data in /tmp + - especially if your disk is spinning media + - and if you're on SSD, this feature extends the life of your flash by reducing your NAND flash writes * Security - sensitive data would be cleared from memory on boot, rather than written (leaked) to disk -- important for encryption scenarios * Power consumption - storing information in memory is more energy efficient than reading and writing to disk In scenarios where more space in /tmp is needed than available, one can compliment that tmpfs with 'sudo apt-get install swapspace' which will - dynamically create/delete swapfile as necessary. + dynamically create/delete swapfile as necessary. See: + http://manpg.es/swapspace
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533639 Title: [ubuntu-cpc] please make /tmp a tmpfs in RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1533639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
