Hello everyone! I wonder whether any other application does a similar thing? /usr/bin/firefox contains this nasty piece: ## ## Use $MOZ_TMPDIR if set. Otherwise use /var/tmp instead of /tmp ## because of 1GB /tmp limit in Fedora 18 and later. ## See: https://bugzilla.redhat.com/show_bug.cgi?id=867073 ## TMPDIR="${MOZ_TMPDIR:-/var/tmp}" export TMPDIR Originally, it had hardcoded TMPDIR to /var/tmp already, overriding the users TMPDIR setting (if any) - https://bugzilla.redhat.com/867073 - and passing that altered env to programs it starts, too. The Firefox source would respect TMPDIR, TEMP and TMP, then fall back to /tmp if no env var is set. Searching a bit in Fedora Wiki pages, I've found: http://fedoraproject.org/wiki/Features/tmp-on-tmpfs > | My CD burning application writes huge .iso files to /tmp, > | and this breaks on tmpfs! > > The application should be fixed to use /var/tmp. > | My application writes temporary files to /tmp and they are > | gone after a reboot! > > The application should be fixed to use /var/tmp. FHS recommends > that /tmp is flushed on reboot, and that's what we do here. It is insane to hardcode /var/tmp. Also, GNOME Shell (F19) here defaults to /tmp, and I guess other parts of the OS do too, not only if they use glib2 (g_get_tmp_dir() or similar). -- Fedora release 19 (Schrödinger’s Cat) - Linux 3.9.3-301.fc19.x86_64 loadavg: 0.02 0.11 0.13 -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
