Hi, On Wed, Feb 03, 2010 at 07:35:31AM -0800, Erich Weiler wrote: > I think I read about this somehwere, but I can't find it now... I > have a cloned service on two nodes that is always running on both > (named, one is a replicated slave). The IP sticks to one, then > floats to the other if the first one goes down. Works great. > > My problem is that named only binds to the IP addrs that are there > when it comes up, so the second node doesn't bind to the floating IP
There's a way to make bind bind to new interfaces. And it even works :) Thanks, Dejan > when it floats over there because bind was already started. If I > restart named after the IP comes over then it works, but that isn't > as automatic as I'd like. ;) > > Is there any way in crm to configure bind to automatically restart > on the second node if it notices the IP floats over to it? > > Thanks for the continued expert advice...! > > -erich > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker