cmap_iter_next(3) [centos man page]
CMAP_ITER_NEXT(3) Corosync Cluster Engine Programmer's Manual CMAP_ITER_NEXT(3) NAME
cmap_iter_next - Return next item in iteration in CMAP SYNOPSIS
#include <corosync/cmap.h> cs_error_t cmap_iter_next(cmap_handle_t handle, cmap_iter_handle_t iter_handle, char key_name[], size_t *value_len, cmap_value_types_t *type); DESCRIPTION
The cmap_iter_next function is used to get next value in iteration. The handle argument is connection to CMAP database obtained by calling cmap_initialize(3) function. iter_handle argument is iterator handle obtained by cmap_iter_init(3) function. Following key name is stored inside key_name argument, which must be preallocated by caller and its quaranted maximum size is CMAP_KEYNAME_MAXLEN (urrently 255). value_len is pointer where length of value is stored, but can be NULL. type is also optional argument (can be NULL) and here type of value is stored (type is one of types described in cmap_get(3) function). RETURN VALUE
This call returns the CS_OK value if successful. If there are no more items to iterate, CS_NO_SECTION error code is returned. SEE ALSO
cmap_iter_init(3), cmap_iter_finalize(3), cmap_initialize(3), cmap_get(3), cmap_overview(8) 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 06/02/2012 CMAP_ITER_NEXT(3)
Check Out this Related Man Page
CMAP_DISPATCH(3) Corosync Cluster Engine Programmer's Manual CMAP_DISPATCH(3) NAME
cmap_dispatch - Dispatches callbacks from the CMAP service SYNOPSIS
#include <corosync/cmap.h> cs_error_t cmap_dispatch (cmap_handle_t handle, cs_dispatch_flags_t dispatch_types); DESCRIPTION
The cmap_dispatch function is used to dispatch configuration changes. Each application may have several connections to the CMAP API. Each application uses the handle argument to uniquely identify the connec- tion. The dispatch_types argument is used to identify the type of dispatch to execute. The possible types are CS_DISPATCH_ONE, CS_DISPATCH_ALL and CS_DISPATCH_BLOCKING. The dispatch values have the following meanings: CS_DISPATCH_ONE Dispatch at least one callback, blocking until the callback is dispatched. CS_DISPATCH_ALL Dispatch all waiting callbacks without blocking to wait for any callbacks. CS_DISPATCH_BLOCKING Dispatch all callbacks blocking indefinitely. This is used in a threaded program where a thread is created, and then cs_dispatch() is called immediately from the created thread to execute callbacks. CS_DISPATCH_ONE_NONBLOCKING Dispatch at most one callback. If there is no pending callback, CS_ERR_TRY_AGAIN is returned. It's needed to call cmap_track_add(3) to add tracked items and receive callbacks. RETURN VALUE
This call returns the CS_OK value if successful, otherwise an error is returned. SEE ALSO
cmap_track_add(3), cmap_track_delete(3), cmap_overview(8) 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 23/01/2012 CMAP_DISPATCH(3)