Claudio Freire wrote:
On Wed, Mar 28, 2012 at 1:09 PM, Graham Anderson
wrote: Of course these two times when software failed due to a full /tmp are in my opinion much preferable to the alternative. The alternative is that when /tmp is a physical volume and badly behaved software fills the whole volume (usually the / volume as well) the whole system is brought to it's knees. This has happened to me often enough from badly written scripts, bugs or software and is the main reason I started using tmpfs /tmp.
Why would it be brought to its knees? Just as tmpfs is, persistent /tmp is also cleaned up (albeit explicitly with a cleanup script) at boot time.
Not by default I think. (not on any of my systems running 12.2Mx)
However I think it does make sense (with tangible benefits) to consider tmpfs /tmp for most desktop users. Lets face it, if you're a power user who is going to be using _large_ amounts of /tmp due to scripts, data manipulation, compiling or using "power apps", you're more than capable of configuring your system to compensate.
I see Firefox + Flash as an issue on this though, what can we do about that?
Easy, configure firefox to use /var/tmp.
Notice that this move will probably require a re-evaluation of the proposed partition schemes in the installer. Now /var will be bigger, /tmp nonexistent, and who knows how that ripples.
Did we ever propose partitions for /var and /tmp? -- Per Jessen, Zürich (17.6°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org