On Tue, Mar 23, 2010 at 9:07 PM, Andreas Mock <[email protected]> wrote: > -----Ursprüngliche Nachricht----- > Von: Andrew Beekhof <[email protected]> > Gesendet: 23.03.2010 20:37:12 > An: Andreas Mock <[email protected]> > Betreff: Re: [Openais] Strange behaviour of corosync >> >>Because the amount of time is determined by whatever resources you're running. >>Someone with a couple of IPs needs only seconds but someone with a >>dozen thumping big databases might need hours. >> >>So almost certainly any chosen period of time will be completely wrong. > > That's an argument... > >>> Because something has gone wrong if corosync is not able to >>> stop properly. Am I wrong? >> >>Yes. Sorry. > > That's nothing new...I'm used to it as it happens from time to time. :-) > > So there's no way to find out that corosync is doing nothing anymore and > could be killed?
Bets thing to do is run "ps axf" on the node. That will tell you which stage its up to. _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
