Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sam_start(3) [centos man page]

SAM_START(3)					    Corosync Cluster Engine Programmer's Manual 				      SAM_START(3)

NAME
sam_start - Start health checking SYNOPSIS
#include <corosync/sam.h> cs_error_t sam_start (void); DESCRIPTION
The sam_start function is used to start health checking of application. After calling this function, the active process needs to send healthchecks within the registered time interval by calling sam_hc_send(3). If event driven healthchecking is configured by calling sam_register(3), an internal thread will be created and send health check confirmations four times per time_interval. Application must be registered by calling sam_register(3) before this function can be called. An application can always stop health checking by calling the sam_stop(3) function. If SAM is initialized with quorum policy SAM_RECOVERY_POLICY_QUIT or SAM_RECOVERY_POLICY_RESTART sam_start will block until corosync becomes quorate. RETURN VALUE
This call return CS_OK value if successful, otherwise and error is returned. If SAM is initialized with quorum policy, returned error can also be quorum error. ERRORS
CS_ERR_BAD_HANDLE component was not registered by calling sam_register(3) function. SEE ALSO
sam_hc_send(3), sam_stop(3), sam_register(3), sam_hc_callback_register(3) CS_ERR_TRY_AGAIN Resource temporarily unavailable CS_ERR_INVALID_PARAM Invalid argument CS_ERR_ACCESS Permission denied CS_ERR_LIBRARY The connection failed CS_ERR_INTERRUPT System call inturrupted by a signal CS_ERR_NOT_SUPPORTED The requested protocol/functuality not supported CS_ERR_MESSAGE_ERROR Incorrect auth message received CS_ERR_NO_MEMORY Not enough memory to completed the requested task corosync Man Page 30/04/2010 SAM_START(3)

Check Out this Related Man Page

VOTEQUORUM_QDEVICE_MASTER_WINS(3)		    Corosync Cluster Engine Programmer's Manual 		 VOTEQUORUM_QDEVICE_MASTER_WINS(3)

NAME
votequorum_qdevice_master_wins - Sets or clears quorum device master_wins flag SYNOPSIS
#include <corosync/votequorum.h> int votequorum_qdevice_master_wins(votequorum_handle_t handle const char name, unsigned int allow); DESCRIPTION
The votequorum_qdevice_master_wins informs votequorum whether or not the currently registered qdevice subsystem supports 'master_wins' mode (default 0). This mode allows the qdevice to effectively take over the quorum calculations of votequorum. Any node with an active qdevice that also has master_wins set becomes quorate regardless of the node votes of the cluster. It is left up to the qdevice subsystem itself (not part of votequorum) to communicate across the nodes or otherwise provide some system of deciding which nodes will be part of the quo- rate cluster, if any. eg They may be the set of nodes that has access to a quorum disk. name The name of the currently registered quorum device on this node. This must match the existing name known to votequorum. allow 0 (the default) means that master_wins is not active on this node. 1 means that master_wins is active on this node. RETURN VALUE
This call returns the CS_OK value if successful, otherwise an error is returned. ERRORS
CS_ERR_TRY_AGAIN Resource temporarily unavailable CS_ERR_INVALID_PARAM Invalid argument CS_ERR_ACCESS Permission denied CS_ERR_LIBRARY The connection failed CS_ERR_INTERRUPT System call inturrupted by a signal CS_ERR_NOT_SUPPORTED The requested protocol/functuality not supported CS_ERR_MESSAGE_ERROR Incorrect auth message received CS_ERR_NO_MEMORY Not enough memory to completed the requested task SEE ALSO
votequorum_overview(8), votequorum_initialize(3), votequorum_finalize(3), votequorum_getinfo(3), votequorum_trackstart(3), votequo- rum_trackstop(3), votequorum_fd_get(3), votequorum_dispatch(3), votequorum_context_set(3), votequorum_context_get(3), votequorum_setex- pected(3), votequorum_setvotes(3), votequorum_qdevice_register(3), votequorum_qdevice_poll(3), votequorum_qdevice_update(3), corosync Man Page 2014-06-10 VOTEQUORUM_QDEVICE_MASTER_WINS(3)
Man Page