On Wednesday 28 March 2012 12:08:33 Frederic Crozat wrote:
Le mercredi 28 mars 2012 à 10:18 +0200, Richard Guenther a écrit :
On Tue, 27 Mar 2012, Frederic Crozat wrote:
Hi all,
this is a announcement regarding changes which have just landed in upstream systemd (not yet released nor pushed to Factory) regarding /media and /tmp: - /media will no longer mounted as tmpfs. This is because udisks2 will no longer use /media for mounting removables devices but /run/media/<user> - /var/run and /var/lock are no longer bind-mounted to /run | /run/lock. We should replace those directories with symlink to /run | /run/lock (probably at initrd time, this is what is done on Fedora) - /tmp is mounted as tmpfs, to make the default setups as stateless as possible. As stated on https://fedoraproject.org/wiki/Features/tmp-on-tmpfs , we might need to fix some applications to use /var/tmp instead of /tmp when they need persistent storage. Another big issue is educating users.
Btw, I see that TMPDIR is /tmp by default on 12.1. GCC uses this for all temporary files, for link-time optimizing firefox for example you need about 4GB of storage in TMPDIR.
Thus, consider that (apart from my own personal opinion that a stateless /tmp is utterly stupid, a tmpfs /tmp is even more so).
So, change TMPDIR to point to /var/tmp? Which would of course make /tmp quite useless.
Indeed, for this use case, it is problematic.
... and for anyone using Inkscape or Gimp or other apps with big files. Oh and flash saves big files in /tmp too. And thumbnailers have a tendency to eat space there. I just removed 1.4 gb of thumbnail files from /tmp. and that's with an 2 day uptime! I already have /tmp mounted tmpfs on my laptop to save the SSD and it very frequently leads to weird problems. I often simply check /tmp if apps are randomly crashing these days... 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... just my few cents...