From owner-freebsd-rc@FreeBSD.ORG Tue Oct 10 10:42:55 2006 Return-Path: X-Original-To: freebsd-rc@FreeBSD.org Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3671A16A40F; Tue, 10 Oct 2006 10:42:55 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39D4E43D6D; Tue, 10 Oct 2006 10:42:50 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id k9AAgEtk022826; Tue, 10 Oct 2006 14:42:14 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id k9AAgEQR022825; Tue, 10 Oct 2006 14:42:14 +0400 (MSD) (envelope-from yar) Date: Tue, 10 Oct 2006 14:42:14 +0400 From: Yar Tikhiy To: Doug Barton Message-ID: <20061010104214.GF12320@comp.chem.msu.su> References: <20061009120756.GA2805@comp.chem.msu.su> <452A9AE0.8090606@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <452A9AE0.8090606@FreeBSD.org> User-Agent: Mutt/1.5.9i Cc: Andrey Simonenko , freebsd-rc@FreeBSD.org Subject: Re: bin/104044: [patch] rc.d/cleartmp works incorrectly X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 10:42:55 -0000 On Mon, Oct 09, 2006 at 11:54:24AM -0700, Doug Barton wrote: > Guys, > > I don't object if you (pl.) decide to tune this up, but please be > aware that it took Brooks and I quite a bit of time to work out The > Right Thing To Do for all the various combinations. Please don't > forget to include both memory backed tmp and permanent disk based tmp > in your testing. Luckily, the CVS history of cleartmp has kept the log of your cuts and tries for us :-) > I'll try to chime in if I can find the time, but right now I'm working > in other areas. One final request, please do not MFC this change > before 6.2-RELEASE unless it has had _at least_ a couple of weeks to > mature first. I feel strongly at this point that rushing this in right > before the release would have more potential to do harm than good. Fully agreed. I'd rather defer the MFC to after 6.2-RELEASE is out. -- Yar