Peter Kruse wrote: > Andrew Beekhof wrote: >> then i'm afraid your use of the "dont fence nodes on startup" option >> has come back to haunt you >> >> beosrv-c-1 came up but was not able to find beosrv-c-2 (even though it >> _was_ running) and because of that option beosrv-c-1 just pretended >> beosrv-c-2 wasn't running and happily started activating resources. >> >> remember how we said that option wasn't a good idea :-) > > Hm, I don't understand, beosrv-c-2 fenced beosrv-c-1 in order > to take over. Now you say, that as soon as beosrv-c-1 came back > up again, it should fence beosrv-c-2, because it "thought" it > was not there, but it was there? How can this happen?
It's a bug :-D. -- Alan Robertson <[EMAIL PROTECTED]> "Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions." - William Wilberforce _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems