On Thu, Mar 19, 2009 at 09:26:03AM +0100, Dejan Muhamedagic wrote: > Hi, > > On Wed, Mar 18, 2009 at 08:24:10PM -0400, Patrick LeBoutillier wrote: > > HI, > > > > >> I'd like to run multiple independant instances of heartbeat on some > > >> hosts. > > >> After looking at the source, it seems the path to the config dir is > > >> hardcoded. > > > > > > why do you think you need to do this? it may be that it's not needed with > > > the newer (2.x) versions of heartbeat. > > > > Here's what I'm trying to do: I have a "farm" of 8 servers. For each > > of my customers there are 2 virtual servers (nodes) dispersed > > throughout the farm. I want to run an instance of heartbeat for each > > customer so that when I add/remove new customers it doesn't impact the > > other ones at the heartbeat level. > > > > I could run heartbeat inside the virtual servers, but then when > > failover occurs I need to reconfigure the network, something that I > > would rather not allow from inside my virtual servers. > > > > If I were to modify heartbeat to be able to change the config dir, > > It is possible to do that at the build/configure time. See > configure --help. > > You'll have to build as many packages as you have customers. I > don't think there's a way around that. AFAIK, nobody tried this > so far, so you may run into issues with duplicate files. Please > report them. > > > would I run into problems running more than one heartbeat (assuming I > > use different UDP ports)? Are there some IPC mechanisms used (shared > > memory, ...) that could be messed up by running multiple instances? > > I think you should be OK.
That is, apart from having a maintenance nightmare. > Thanks, > > Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
