quorum_trackstart(3) [centos man page]
QUORUM_TRACKSTART(3) Corosync Cluster Engine Programmer's Manual QUORUM_TRACKSTART(3) NAME
quorum_trackstart - Enable callbacks notification. SYNOPSIS
#include <corosync/quorum.h> int quorum_trackstart(quorum_handle_t *handle, unsigned int flags); DESCRIPTION
The quorum_trackstart function is used to enable callbacks notification from the quorum API. Every time the voting configuraton changes (eg a node joins or leave the cluster) or the quorum status change, the notification is queued. The notification is dispatched via quorum_dispatch() function that will execute the callback. The flags argument is defined by one or more of the following values and values can be bitwise-or'd #define CS_TRACK_CURRENT 0x01 #define CS_TRACK_CHANGES 0x02 #define CS_TRACK_CHANGES_ONLY 0x04 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
quorum_overview(8), quorum_initialize(3), quorum_finalize(3), quorum_getquorate(3), quorum_trackstop(3), quorum_fd_get(3), quorum_dis- patch(3), quorum_context_set(3), quorum_context_get(3) corosync Man Page 2014-06-10 QUORUM_TRACKSTART(3)
Check Out this Related Man Page
VOTEQUORUM_QDEVICE_REGISTER(3) Corosync Cluster Engine Programmer's Manual VOTEQUORUM_QDEVICE_REGISTER(3) NAME
votequorum_qdevice_register - Registers a new quorum device SYNOPSIS
#include <corosync/votequorum.h> int votequorum_qdevice_register(votequorum_handle_t handle, const char * name); DESCRIPTION
The votequorum_qdevice_register is used to register a new quorum device. A quorum device is an external way of adding votes to a small cluster. The quorum device is, in effect, a pseudo node in the cluster that provide votes based on some external device, usually a shared disk partition or perhaps a network router. This call creates the device but does not mark it active. votequorum_qdevice_poll must be called for the votes to be included in the quo- rum calculation. name is string containing an informative name for the quorum device. It is simply stored by votequorum and used in the display of corosync- quorumtool, it can be a maximum of 254 characters. The number of votes contributed by the quorum device is already known to votequorum, it is set in cmap quorum.device.votes and not by the device. Note that it is the responsibility of the quorum device subsystem (not provided as part of votequorum) to keep all nodes informed of the quorum device status. 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_unregister(3), votequorum_qdevice_poll(3), votequorum_qdevice_update(3), votequo- rum_qdevice_master_wins(3) corosync Man Page 2014-06-10 VOTEQUORUM_QDEVICE_REGISTER(3)