On Thu, Jun 28, 2007 at 02:33:42PM -0400, Lon Hohberger wrote: > (1) don't start rgmanager on the fifth node :), or ...now there's an idea :) > (2) if you do start rgmanager on the fifth node, make all services be > part of a "restricted" failover domain comprised of the other four > nodes. > > > Or > > should I just make sure that the fifth member always comes up last (that > > is, won't be running while the others are coming up)? Or should I aceept > > that I'm going to create more harm than avoiding by letting the fifth > > node belong to the cluster, and just run it outside the cluster? > > If the above two don't work, it's a bug. If (2) means /all/ the services, even the one that should be running on the fifth node, it's more or less equal to (1), isn't it? That is, the service that I want to be running on node five can't be a clustered service (which is, come to think of it, exactly what I want...) > (Oh! and those status-script checks will be fixed in 5.1 ;) ). (Thanks.) --Janne -- Janne Peltonen <janne.peltonen@xxxxxxxxxxx> -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
