Date: Thu, 18 May 2006 11:38:01 -0400 (EDT) From: "Brian A. Seklecki" <lavalamp@spiritual-machines.org> To: freebsd-rc@freebsd.org Cc: General Linux-HA mailing list <linux-ha@lists.linux-ha.org> Subject: Re: Integrating OCF framework w/ (Net|Free)BSD rc.d Message-ID: <20060518113707.C82296@arbitor.digitalfreaks.org>
next in thread | raw e-mail | index | archive | help
On Tue, 16 May 2006, joerg@britannica.bec.de wrote: > On Tue, May 16, 2006 at 01:35:51PM -0400, Brian A. Seklecki wrote: > [SNIP] >> >> I'm interested in any discussion / thoughts on a strategy or apporach for >> coding OCF compatibility / integration into our rc.d/ system > > Oh my god, another over-complicated Linux "standard" which uses the A lot of this goes without saying. However, Linux-HA is the only available, portable Failover Management Software (FMS) available for POSIX compliant systems. It's under active development and the 2.x branch has some game. I'm not talking about changing any default behavior, I'm asking what the best strategy would be to put hooks in place to easily enable "compatibility" mode. Adding new commands is easy with $extra_commands, but changing return codes requires some if[]'s in-tree. An extra couple of cycles blown isn't that bad of a tradeoff to bring high availability (HA) / failover features to *BSD. ~BAS > kitchen sink approach for system management. I'm strongly opposing > changing the current system to comply with this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060518113707.C82296>