
Le jeudi 29 mars 2012 à 10:54 +0200, Richard Guenther a écrit :
On Wed, 28 Mar 2012, Frederic Crozat wrote:
Le mercredi 28 mars 2012 à 11:41 -0300, Claudio Freire a écrit :
On Wed, Mar 28, 2012 at 11:38 AM, Jos Poortvliet <jos@opensuse.org> wrote:
In short, I would STRONGLY recommend against mounting /tmp tmpfs. That ONLY works for advanced users as they can fix the resulting problems themselves. Anyone who keeps their PC on for a longer period of time will see that folder grow and grow and grow. Eating memory instead of diskspace is bad in itself, running out of space there is worse...
I recommend the opposite. I recommend doing this move with a small tmpfs early in the release cycle, so that testers can weed out misbehaving apps (like gimp). Those apps should be using /var/tmp.
To be more precise, Lennart (systemd author) has put some developer oriented informations about /tmp in a post blog :
Hmm.
6. Otherwise use $TMPDIR with a fallback on /var/tmp. Also use mkstemp()/mkdtemp().
that's what the GCC case applies to. Which means $TMPDIR be better _not_ /tmp.
?
With tmpfs /tmp, probably, regarding the memory usage of it.. Feel free to discuss the topic with Lennart in the comments on the page. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org