On Sat, 22 Sep 2001, Adam Bower wrote:

> On Sat, 22 Sep 2001, Jeffrey W. Baker wrote:
>
> > Hey, don't delete my fucking work, just because I happen to have put it in
> > /tmp.  /tmp means "temporary", it doesn't mean "delete upon reboot".  If
> > you want that, how about "/gets-deleted-at-reboot".  DUH.  /tmp on Linux
> > is not some stupid communist shit-licking in-memory filesystem like it is
> > on Solaris.  And if I find the fuckbag who wrote the script that delted my
> > work, I'm going to give him a piece of my mind.
>
> You do not know the difference between /tmp then and /var/tmp it is a very
> well recognised way of doing things for a long time now.
>
> /tmp means do not persist over a reboot
> /var/tmp means do persist over a reboot

That's all well and good, but there's no reason whatever to clear out /tmp
if the machine shutdown unexpectedly.  If you ABSOLUTELY INSIST on
clearing /tmp, put it in the shutdown scripts not the bootup scripts.

It's a completely stupid and useless policy that doesn't help one lick for
long-living systems (the majority of Unix systems, at least all the ones
I've ever used).  Clearing /tmp on boot is traditional (indeed, implied
and unavoidable) WHEN /tmp is mounted on a memory file system, otherwise
it is insipid.

I have a good policy: delete /tmp files that haven't been accessed in over
7 days, only if the device upon which /tmp is mounted has passed some free
space low water mark.

-jwb

Reply via email to