On Fri, Jul 10, Jan Engelhardt wrote:
/tmp is one of the weirder places in a system.
It is nice that FHS says it is not persistent across reboots, but if you have a workstation or server which is "never" (or at least, seldomly) rebooted, the directory can still fill up - and take away RAM from both oneself and other users.
We analyzed many systems for that. On standard servers (if the admin does not do stupid things like storing many installations DVD in /tmp or so or use it as Desktop), /tmp is nearly empty.
Firefox for example has the very bad habit of dumping all its .xpi file downloads into /tmp, and not cleaning them.
Firefox is the only left over application writing things in /tmp and don't clean up for a long time on standard installations. The second one is "go", if you abort the build process. But that's the exception.
Users have bad habit :^) in abusing /tmp as the shortest way to store a file in a known location for some time - because any other location would be persistent (but /tmp might be too heh) and the path much longer.
Now they have to learn that they have a home directory for storing files and /tmp was always a bad idea. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org