From owner-freebsd-bugs Sat Nov 15 12:57:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01040 for bugs-outgoing; Sat, 15 Nov 1997 12:57:41 -0800 (PST) (envelope-from owner-freebsd-bugs) Received: from fly.HiWAAY.net (sprice@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01005 for ; Sat, 15 Nov 1997 12:57:38 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by fly.HiWAAY.net (8.8.7/8.8.6) with SMTP id OAA18167; Sat, 15 Nov 1997 14:57:33 -0600 (CST) Date: Sat, 15 Nov 1997 14:57:33 -0600 (CST) From: Steve Price To: Evan Champion 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, Evan Champion wrote: # On Sat, 15 Nov 1997, Steve Price wrote: # # Well, not quite, since that only gets run out of crontab. Something # should be run on boot, and it needs to nuke everything (except the # exclusions mentionned in my original post, ie: quotas and lost+found). # I guess that is a matter of preference really. I personally don't clear /tmp on any of my machines, preferring to clean them manually. I keep alot of stuff that I don't want toasted in /tmp and since power outtages seem to happen frequently around here and I don't have a UPS (yet) 'cleaning /tmp' is of no use to me. That doesn't mean it is not the right thing to do in certain circumstances as I am sure you can attest. I would guess that the premise is that having to reboot a machine is a very infrequent occurrence (at least with anything not MSoft that is) and doing this as a cron job will allow the system administrator to choose the frequency with which cleanings of /tmp occur and not leave it up to fate or some other ill-fated reason. Steve # Evan # #