ocf_heartbeat_Xinetd (7) Linux Manual Page

The xinetd daemon itself must be running: we are not going to start or stop it ourselves.

All services should have a line saying either "disable=yes" or "disable=no". The script just changes those settings before reloading xinetd.

Important: in case the services managed by the cluster are the only ones enabled, you should specify the -stayalive option for xinetd or it will exit on Heartbeat stop. Alternatively, you may enable some internal service such as echo.

Supported Parameters

service

The name of the service managed by xinetd.

(required, string, no default)

Supported Actions

This resource agent supports the following actions (operations):

start

Starts the resource. Suggested minimum timeout: 20s.

stop

Stops the resource. Suggested minimum timeout: 20s.

restart

Suggested minimum timeout: 20s.

status

Performs a status check. Suggested minimum timeout: 10. Suggested interval: 10.

monitor

Performs a detailed status check. Suggested minimum timeout: 10. Suggested interval: 10.

validate-all

Performs a validation of the resource configuration. Suggested minimum timeout: 5.

meta-data

Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.

Example Crm Shell

The following is an example configuration for a Xinetd resource using the crm(8) shell:

primitive p_Xinetd ocf:heartbeat:Xinetd \
 params \
 service=string \
 op monitor depth="0" timeout="10" interval="10" 

Example Pcs

The following is an example configuration for a Xinetd resource using pcs(8)

pcs resource create p_Xinetd ocf:heartbeat:Xinetd \
 service=string \
 op monitor depth="0" timeout="10" interval="10" 

See Also

m[blue]http://www.linux-ha.org/wiki/Xinetd_(resource_agent)m[]

Author

Linux-HA contributors (see the resource agent source for information about individual authors)