On 06/07/2011 07:09 PM, CeR wrote: > Hi there! > > I have some doubts, hope you folks can help me. > > In a system I have two (or more) ways to start a daemon: > A) /etc/init.d/ script. The service could be started by the system > (/etc/rcX) or by me manually. > B) The daemon has an executable with an argument option to run it as a > daemon (like conntrackd, openvpn and many others) > C) Other resources doesn't need /etc/init.d script nor an argument to > run as a demon (at least IPaddr and IPv6addr) > > In the other hand, we have the OCF resource agent, who manage the > service (start in one node, stop in another or whatever). > > What is really needed by the cluster stack to work well?
The agent, be it an OCF or LSB agent, has to implement the return code specs (ie start an already started resource has to return a certain value). You can read about OCF agent return code specs here: http://linux-ha.org/doc/dev-guides/ra-dev-guide.html LSB is here: http://www.linux-ha.org/wiki/LSB_Resource_Agents Regards Dominik > It depends of > the concrete case? I have take look into some RA and I see that some > resources are controlled directly with the binary. But i set up a > cluster that didn't work well until I put the /etc/init.d script. > > Could you give me some clues? Maybe some documentation to read on about this? > > Best regards! > _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
