On Fri, Jun 01, 2012 at 11:05:26AM -0400, Gregory Maxwell wrote:
On Fri, Jun 1, 2012 at 9:50 AM, Gerry Reno <greno(a)verizon.net>
wrote:
> So everyone needs to go out and buy twice as much RAM so F18+ can run /tmp as tmpfs
without causing memory shortfalls
> for everything else they do.
> That's crazy.
Thats not true (and I've used tmpfs for tmp for years, so I'm speaking
from experience)— tmpfs is backed by swap on demand. Just add the
space that you would have used for /tmp to your swap.
The *default* limit for tmpfs is half of physical RAM (swap is not
counted). So *if* tmp-on-tmpfs is left at the defaults then
increasing physical RAM might be necessary. I haven't bothered to
look at how tmp-on-tmpfs is implemented in systemd though.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top