Date: Wed, 16 Jul 2008 22:08:19 -0400 From: David Schultz <das@FreeBSD.ORG> To: Dimitry Andric <dimitry@andric.com> Cc: Doug Barton <dougb@FreeBSD.ORG>, Dan Nelson <dnelson@allantgroup.com>, freebsd-current@FreeBSD.ORG Subject: Re: Heads Up: shutdown keyword added to 34 rc.d scripts. Message-ID: <20080717020819.GA22145@zim.MIT.EDU> In-Reply-To: <487E7364.2040909@andric.com> References: <487E533F.7050303@FreeBSD.org> <20080716201819.GB19044@dan.emsphone.com> <487E5DCD.3010206@FreeBSD.org> <20080716210306.GA20758@zim.MIT.EDU> <487E71B4.305@andric.com> <487E7364.2040909@andric.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 17, 2008, Dimitry Andric wrote: > On 2008-07-17 00:09, Dimitry Andric wrote: > > Possibly just the "reverse" of the startup deps? > > Ah, I just see this in rc(8): > > Operation of rc.shutdown > ... > 3. Invoke rcorder(8) to order the files in /etc/rc.d/ and the > $local_startup directories that have a ``shutdown'' KEYWORD (refer > to rcorder(8)'s -k flag), reverse that order, and assign the result > to a variable. > > e.g. it's already taken care of, apparently. :) This just reverses the startup deps, as you suggested earlier. I seem to recall that there was at least one example from Solaris where that was the wrong thing to do. (Clearly it's also overly conservative in some cases.) But they were trying to do more sophistocated things as well, such as automatically restart failed services. (This isn't trivial because when services depend on each other, it's hard to tell which one failed, and it may even take some trial and error.) Maybe we just haven't run into any situations where it matters.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080717020819.GA22145>