From owner-freebsd-bugs Sat Nov 15 18:27:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA11319 for bugs-outgoing; Sat, 15 Nov 1997 18:27:58 -0800 (PST) (envelope-from owner-freebsd-bugs) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA11306 for ; Sat, 15 Nov 1997 18:27:42 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 7575 invoked from network); 16 Nov 1997 02:27:31 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 16 Nov 1997 02:27:31 -0000 Date: Sat, 15 Nov 1997 21:27:30 -0500 (EST) From: Evan Champion To: Steve Price cc: freebsd-bugs@hub.freebsd.org Subject: Re: misc/5054: /tmp not nuked on reboot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 15 Nov 1997, Steve Price wrote: > IMHO, cleaning /tmp or any files for that matter without me, the system > administrator, having explicitly told it to do so smells of anarchy. I > wished I had the power to reverse such things as this, but this seems > to be a policy decision that the core group has made and the best place > to plead your case is with them. I'm pretty sure that at least Jordan > is following this thread and will chime in at any moment and clue both > of us in as to why this functionality was removed. :) My guess is that it was removed because people who didn't understand what /tmp was for were losing files. Otherwise there really wasn't any reason to change it :-) > Please don't take this the wrong way. I tried to offer you an alternative > solution that would accomplish what you wanted. If my solution does not > suit your needs, feel free to develop your own or revert back to the > legacy way of doing things. As for getting this change reverted in > FreeBSD, we will have to wait and see what some of the others have > to say. I know that this is something that a lot of people like and a lot of people hate. Fortunately, that is why /etc/rc.conf exists, so that you can configure what _you_ want the system to do. What I'd like to see is for this to become an option in /etc/rc.conf. That way those who want it can and those who don't just don't set that option. Evan