On Tue, Mar 27, 2012 at 8:20 PM, Cristian Rodríguez
(And yes, I have /tmp as tmpfs on my 6G-of-RAM machine.)
BTW stateless /tmp can be achieved by rm -rf /tmp/* at each boot.
A more important matter is... how does the distribution guarantee correct behavior on low-memory systems?
You can use more swap, and zcache (if it worked with our current kernels, unfortunately it does not)
You're missing the point. Even if users have the choice to explicitly override this, the defaults on a distribution should be sensible and able to run on the largest base possible. Many server setups explicitly avoid swap because of the performance impact it entails, many regular users do that too, and many programs misbehave in the sense that they write massive amounts of data in /tmp. In low memory devices, with /tmp as tmpfs, think 1G, brasero, k3b and a few other programs, in their default configuration, would thrash. Those are blatantly wrong cases. But there are numerous gray cases. Python's tempfile module creates, by default, files in /tmp. I would bet tons of python apps, thus, misuse /tmp. You *have* to make /tmp small in that case, to make sure those programs break, and to make sure those programs don't eat available RAM. It's the only way to forcibly fix them. Otherwise, testers won't be able to test unless they install on a VM with 128M of RAM. And this is assuming users can override this decision and use a regular filesystem as /tmp. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org