Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #132
Difficulty: Easy
Many of the command line and graphical utilities in a Linux distro are very similar to a Unix system.
True or False?
Linux & Unix Commands - Search Man Pages

heartbeat(8) [debian man page]

HEARTBEAT(8)						  System administration utilitie					      HEARTBEAT(8)

NAME
heartbeat - Heartbeat subsystem for High-Availability Linux DESCRIPTION
heartbeat is a basic heartbeat subsystem for Linux-HA. It will run scripts at initialisation, and when machines go up or down. This version will also perform IP address takeover using gratuitous ARPs. It works correctly for a 2-node configuration, and is extensible to larger configurations. It implements the following kinds of heartbeats: o UDP/IP broadcast; o UDP/IP multicast; o UDP/IP unicast; o Bidirectional Serial Rings ("raw" serial ports) -- this type is deprecated and should no longer be used; o special "ping" heartbeats for routers, etc. -- this type has been superseded by functionality in pacemaker() and should no longer be used. Comprehensive documentation on heartbeat is available in the Heartbeat User's Guide. If this documentation is not installed on your system, it can be found at http://linux-ha.org/. OPTIONS
The following options are supported by heartbeat: -d Increment debugging level. Higher levels are more verbose. -r Reload heartbeat. This option is functionally identical to sending a running heartbeat process a HUP signal. If the configuration has not changed, then this option is essentially a no-op. If ha.cf(5) or authkeys(5) has changed, then heartbeat will re-read these files and update its configuration. This option may not be used together with -R. -k Kill (stop) heartbeat. -s Report heartbeat status. -R Heartbeat restart exec flag (internal use only). May not be used with -r. -C Heartbeat current resource state for restart (internal use only). Only valid with -R. -V Print out heartbeat version. Note that most of these options are used for supporting the heartbeat init script, which provides the conventional start, stop, status and restart options (among others). It is recommended to use this rather than invoking the heartbeat command directly. SEE ALSO
ha.cf(5), authkeys(5) AUTHORS
Alan Robertson <alanr@unix.sh> heartbeat Juan Pedro Paredes Caballero <juampe@retemail.es> man page Simon Horman <horms@verge.net.au> man page Florian Haas <florian.haas@linbit.com> man page Heartbeat 3.0.5 24 Nov 2009 HEARTBEAT(8)

Check Out this Related Man Page

OCF_HEARTBEAT_XINETD(7) 					OCF resource agents					   OCF_HEARTBEAT_XINETD(7)

NAME
ocf_heartbeat_Xinetd - Manages a service of Xinetd SYNOPSIS
Xinetd [start | stop | status | monitor | meta-data | validate-all] DESCRIPTION
Resource script for Xinetd. It starts/stops services managed by xinetd by enabling or disabling them in the configuration file. 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
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" SEE ALSO
http://www.linux-ha.org/wiki/Xinetd_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_XINETD(7)

Featured Tech Videos