> > Ok, then the reason for the restart is that the resource definition > changed (the value of the is-managed "attribute" changed requiring a > restart). > By using --meta, you're telling the cluster that this is an option for > the PE - not the resource. This puts it in a different namespace > which doesn't influence restarts. > > Btw. In 1.0 you can put the whole cluster into maintenance mode by > setting the global maintenance-mode attribute. > This differs from is-managed in that it will also automatically cancel > any recurring monitor actions (preventing the cluster from even > noticing if anything fails).
Ohh - okay. I will go read the dtd, this sounds like a real 'freeze'. > > Perhaps that helps. > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
