Originally Posted by unSpawn
Yes but that's not my point. It's about what tasks one may expect a system to perform on bootup. Yours wipes everything, without regard for anything and without a user being able to stop it.
Yes -- it wipes everything.
I'm not sure what you are saying with "without a user being able to stop it
". Assuming no show-stopping errors, that is the case with all boot processes -- or are you saying it should be configurable?
I vaguely recall that wiping everything was the default behaviour of some UNIX implementations but I can't find any references to back that up.
The only other Linux I have inspected is ubuntu 8.04 desktop and its default behaviour is to remove everything except the following if they are owned by root
"lost+found" make a lot of sense (!); ".clean" is the cleanup routine's own marker file; "*quota*" will presumably only be relevant if /tmp is a mount point and quotas are implemented; I don't know about ".journal" and "...security" but have never seen them.
In my initial post I asked "are there any reasons for not deleting everything in /tmp as soon as it is mounted?" On the basis of further information I would now like to change that to "Are there any reasons for not deleting everything in /tmp (except, if it is a mount point, "lost+found" and, if it is a mount point, quota files if quotas are implemented) as soon as it is mounted and writeable?