Hi Andrew, > Ok, but I'm trying to understand why.
Thank you. > What function are these daemons performing? Why do they need to keep > running even when the node is in standby? For example, respawn can detect the abnormality of the node before becoming online by detecting trouble in standby. In a sense it has the same effect to start pingd in respawn. In respawn which users made in imitation of pingd, what a function to detect in this standby state is included in will be expected. Best Regards, Hideo Yamauchi. --- Andrew Beekhof <and...@beekhof.net> wrote: > On Mon, Sep 21, 2009 at 2:54 PM, <renayama19661...@ybb.ne.jp> wrote: > > Hi Andrew, > > > >> I'm almost afraid to ask, why would someone need this capability? > > > > In the case of the environment that shifted from version 1 of Heartbeat, I > > think that the user > may do > > how to use such respawn. > > Ok, but I'm trying to understand why. > What function are these daemons performing? Why do they need to keep > running even when the node is in standby? > > > > > We talk about a substitute method again, too. > > > > Thank you. > > Hideo Yamauchi. > > > > --- Andrew Beekhof <and...@beekhof.net> wrote: > > > >> On Fri, Sep 18, 2009 at 3:09 AM, �<renayama19661...@ybb.ne.jp> > >> wrote: > >> > Hi Andrew, > >> > > >> >> I still don't understand why you can't simply make them regular > >> >> cluster resources. > >> >> Can you please explain? > >> > > >> > I understand your opinion. > >> > I surely understand that simple RA can operate an object of respawn by > >> > shifting. > >> > > >> > However, an object of respawn of all users cannot shift to RA. > >> > For example, there is the user who does respawn of processing to work > >> > even if a node > becomes > >> the > >> > standby state. > >> > >> I'm almost afraid to ask, why would someone need this capability? > >> > >> > But, a primitive resource and the Clone resource stop when a node > >> > becomes the standby > state. > >> > The user needing this respawn cannot easily shift to new environment. > >> > >> True. > >> > >> _______________________________________________ > >> 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 > > > > _______________________________________________ > 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