That way you just select the init script from your init.d and thats it.
Probably you will need to change config path but this depends on your cluster architecture.
Like greg said, there are some init.d scripts that do not return 0, so heartbeat will try to re-launch services over and over again :-)
Daniel -- Daniel Grilo Partner of Grupo PDM Av. Conde Valbom 30, 3o 1050-068 Lisboa (Portugal) web: http://www.pdmfc.com Tel: +351 21 357 20 29 // mobile: +351 91 388 94 39 (ext: 716) Fax: +351 21 357 20 31 Confidencialidade Esta mensagem, bem como os documentos que a acompanham, podem conter informações confidenciais ou privilegiadas. Se receber esta mensagem por erro, ou não for o destinatário, deverá apagá-la, assim como, os ficheiros anexos ou cópias. Qualquer utilização parcial, comentário, cópia, distribuição ou qualquer acção baseada nesta informação é estritamente proibida. Se, por erro, recebeu esta informação, queira informar-nos. Obrigado pela sua colaboração. The information in this message is confidential and privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it is prohibited. Please contact immediately the sender if you have received this message by error. Thank you. -------- Random Quote ------- Artistic ventures highlighted. Rob a museum. On 09/08/2010 10:35 PM, Greg Woods wrote:
On Wed, 2010-09-08 at 14:18 -0500, Bradley Leduc wrote:Am trying to add NAMED and DHCPD services as a resource on heartbeat-3.0.1-1.el5 cluster with no luck, I was wondering if anyone would know of an easy to do this. Any help would be great.Are you running pacemaker or just a heartbeat v1-style config? I've done it both ways. For v1 all I did was add "dhcpd" to haresources. For pacemaker, I use the ocf:heartbeat:anything resource since I couldn't find one specific to named or dhcpd anywhere. So I have config lines like this: primitive dhcp ocf:heartbeat:anything \ params binfile="/usr/sbin/dhcpd" cmdline_options="-f" \ op monitor interval="10" timeout="50" depth="0" \ op start interval="0" timeout="90s" \ op stop interval="0" timeout="100s" \ meta target-role="Started" named works similarly. For v1, you may need to create a resource.d script that properly returns 0 if you try to stop a daemon that is already stopped; the standard init.d startup scripts don't always do this. --Greg _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
<<attachment: daniel_grilo.vcf>>
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
