From owner-freebsd-current@FreeBSD.ORG Wed Jul 16 22:09:59 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F3E01065674; Wed, 16 Jul 2008 22:09:59 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2DC118FC1F; Wed, 16 Jul 2008 22:09:59 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:4889:afda:a548:e04] (unknown [IPv6:2001:7b8:3a7:0:4889:afda:a548:e04]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 22B983C; Thu, 17 Jul 2008 00:09:58 +0200 (CEST) Message-ID: <487E71B4.305@andric.com> Date: Thu, 17 Jul 2008 00:09:56 +0200 From: Dimitry Andric User-Agent: Thunderbird 2.0.0.17pre (Windows/20080712) MIME-Version: 1.0 To: Doug Barton , Dan Nelson , freebsd-current@FreeBSD.ORG References: <487E533F.7050303@FreeBSD.org> <20080716201819.GB19044@dan.emsphone.com> <487E5DCD.3010206@FreeBSD.org> <20080716210306.GA20758@zim.MIT.EDU> In-Reply-To: <20080716210306.GA20758@zim.MIT.EDU> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Heads Up: shutdown keyword added to 34 rc.d scripts. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 22:09:59 -0000 On 2008-07-16 23:03, David Schultz wrote: > A niftier trick would be to actually denote the shutdown > dependencies between apps. Then SIGTERM (or whatever the > appropriate shutdown operation is) can happen in parallel as much > as possible, without accidentally shutting down a service before > dependent services have had a chance to clean up. There's probably > not as many interesting deps for shutdown as there are for > startup... Possibly just the "reverse" of the startup deps? For example, if baz is dependent on foo and bar, the startup order is: 1. foo & bar (possibly parallel) 2. baz at shutdown, we'd get the reverse: 1. baz 2. foo & bar (possibly parallel) However, this may not be so easy for the total dependency graph of everything under /etc/rc.d (not to forget /usr/local/etc/rc.d). ;)