From owner-freebsd-stable@FreeBSD.ORG Mon Jan 22 00:32:29 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF37B16A400 for ; Mon, 22 Jan 2007 00:32:29 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 2C5DB13C455 for ; Mon, 22 Jan 2007 00:32:29 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 3533 invoked by uid 399); 22 Jan 2007 00:32:28 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 22 Jan 2007 00:32:28 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45B40619.30206@FreeBSD.org> Date: Sun, 21 Jan 2007 16:32:25 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <1169038057.23831.24.camel@richard02> <20070117142552.GC1225@dkirhlarov.mow.oilspace.com> <1169044590.23831.38.camel@richard02> <45AE68DF.5010700@FreeBSD.org> <1169110278.20706.58.camel@chaffinch> <20070119170012.GB1532@roadrunner.q.local> In-Reply-To: <20070119170012.GB1532@roadrunner.q.local> X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Failover-HA-Setup X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 00:32:29 -0000 Ulrich Spoerlein wrote: > Only two options remain: modify existing mysql-server script (bad idea, > will be overwritten on update) or go through a proxy script which > "transforms" start|stop -> onestart|onestop > > You could also alter the environment of heartbeat (it's really just a > bunch of poorly written shell scripts) and set mysql_enable=YES there, > but that'd be just as fragile as rewriting the existing mysql-server > script. Yeah, I thin we're definitely in territory that is not covered by the boot scripts as written here. This thread has got me thinking though, how useful would something like 'foo_enable=conditional' be? What I'm thinking is that you could define a script in foo_condition that rc.d would run. We could either do a straight yes/no, where if the script exits successfully (exit code 0) then we run the service, and if it fails (non-zero exit code) we don't. OR, we could have the script return the argument we want to feed that service's startup script. I think that may have some utility here, what do y'all think? Doug -- This .signature sanitized for your protection