Date: Mon, 5 Oct 2009 09:58:42 -0400 From: Wesley Shields <wxs@FreeBSD.org> To: Doug Barton <dougb@FreeBSD.org> Cc: Alex Trull <alex@trull.org>, freebsd-rc@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: (Ab)using rcng's features to keep rc.d-style services running should they fail. Message-ID: <20091005135842.GA8629@atarininja.org> In-Reply-To: <4AC8F7EF.9010303@FreeBSD.org> References: <20091004141118.GG95662@syndicate.internationalconspiracy.org> <4AC8F7EF.9010303@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 04, 2009 at 12:30:55PM -0700, Doug Barton wrote: > Alex Trull wrote: > > Hi all, > > > > I realised that because portupgrade/portmaster don't always > > cleanly restart processes that have died due to being > > upgraded (mysqld, often!) that this was something I wanted > > to fix. > > I can't speak to portupgrade, however for portmaster there is no such > facility whatsoever. The admin is expected to disable things prior to > an upgrade and re-enable them when the upgrade is done. I don't feel > that this is an overwhelming burden. :) There is the @stopdaemon directive in plists (which gets translated into @unexec to forcestop the script). Some ports use it and some do not. Personally I think ports doing this automatically are quite annoying, and would love to rip them all out from the ports. Something like portmaster growing support for it would be welcome provided it does not happen by default. I've always found it funny that there is no @startdaemon directive (rightfully so, as we want people to explicitly turn things on) but it's acceptable if things get turned off via @stopdaemon without explicit permission. If a particular upgrade requires that the thing be not running we should check for that and abort, not go shutting things down. -- WXS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091005135842.GA8629>