upscli_get(3) [posix man page]

UPSCLI_GET(3)							    NUT Manual							     UPSCLI_GET(3)

NAME

       upscli_get - retrieve data from a UPS

SYNOPSIS

       #include <upsclient.h>

       int upscli_get(UPSCONN_t *ups, int numq, const char **query,
			      int *numa, char ***answer)

DESCRIPTION

       The upscli_get() function takes the pointer ups to a UPSCONN_t state structure, and the pointer query to an array of numq query elements.
       It builds a properly-formatted request from those elements and transmits it to upsd(8).

       Upon success, the response will be split into separate components. A pointer to those components will be returned in answer. The number of
       usable answer components will be returned in numa.

USES

       This function implements the "GET" command in the protocol. As a result, you can use it to request many different things from the server.
       Some examples are:

       o   GET NUMLOGINS <ups>

       o   GET UPSDESC <ups>

       o   GET VAR <ups> <var>

       o   GET TYPE <ups> <var>

       o   GET DESC <ups> <var>

       o   GET CMDDESC <ups> <cmd>

QUERY FORMATTING

       To generate a request for GET NUMLOGINS su700, you would populate query and numq as follows:

	   int numq;
	   const char *query[2];

	   query[0] = "NUMLOGINS";
	   query[1] = "su700";
	   numq = 2;

       All escaping of special characters and quoting of elements with spaces is handled for you inside this function.

ANSWER FORMATTING

       The raw response from upsd to the above query would be NUMLOGINS su700 1. Since this is split up for you, the values work out like this:

	   numa = 3;
	   answer[0] = "NUMLOGINS"
	   answer[1] = "su700"
	   answer[2] = "1"

       Notice that the value which you seek typically starts at answer[numq].

ERROR CHECKING

       This function will check your query against the response from upsd(8). For example, if you send "VAR" "su700" "ups.status", it will expect
       to see those at the beginning of the response.

       If the results from upsd do not pass this case-insensitive test against your request, this function will return an error. When this
       happens, upscli_upserror(3) will return UPSCLI_ERR_PROTOCOL.

ANSWER ARRAY LIFETIME

       The pointers contained within the answer array are only valid until the next call to a upsclient function which references them. If you
       need to use data from multiple calls, you must copy it somewhere else first.

       The answer array and its elements may change locations, so you must not rely on previous addresses. You must only use the addresses which
       were returned by the most recent call. You also must not attempt to use more than numa elements in answer. Such behavior is undefined, and
       may yield bogus data or a crash.

       The array will be deleted after calling upscli_disconnect(3). Any access after that point is also undefined.

RETURN VALUE

       The upscli_get() function returns 0 on success, or -1 if an error occurs.

SEE ALSO

       upscli_list_start(3), upscli_list_next(3), upscli_strerror(3), upscli_upserror(3)

Network UPS Tools						    05/22/2012							     UPSCLI_GET(3)

Check Out this Related Man Page

UPSCLI_LIST_START(3)						    NUT Manual						      UPSCLI_LIST_START(3)

NAME

       upscli_list_start - begin multi-item retrieval from a UPS

SYNOPSIS

       #include <upsclient.h>
       int upscli_list_start(UPSCONN_t *ups, int numq, const char **query)

DESCRIPTION

       The upscli_list_start() function takes the pointer ups to a UPSCONN_t state structure, and the pointer query to an array of numq query
       elements. It builds a properly-formatted request from those elements and transmits it to upsd(8).

       Upon success, the caller must call upscli_list_next(3) to retrieve the elements of the list. Failure to retrieve the list will most likely
       result in the client getting out of sync with the server due to buffered data.

USES

       This function implements the "LIST" command in the protocol. As a result, you can use it to request many different things from the server.
       Some examples are:

       o   LIST UPS

       o   LIST VAR <ups>

       o   LIST RW <ups>

       o   LIST CMD <ups>

       o   LIST ENUM <ups> <var>

       o   LIST RANGE <ups> <var>

QUERY FORMATTING

       To see the list of variables on a UPS called su700, the protocol command would be LIST VAR su700. To start that list with this function,
       you would populate query and numq as follows:

	   int numq;
	   const char *query[2];

	   query[0] = "VAR";
	   query[1] = "su700";
	   numq = 2;

       All escaping of special characters and quoting of elements with spaces are handled for you inside this function.

ERROR CHECKING

       This function checks the response from upsd(8) against your query. If it is not starting a list, or is starting the wrong type of list, it
       will return an error code.

       When this happens, upscli_upserror(3) will return UPSCLI_ERR_PROTOCOL.

RETURN VALUE

       The upscli_list_start() function returns 0 on success, or -1 if an error occurs.

SEE ALSO

       upscli_fd(3), upscli_get(3), upscli_readline(3), upscli_sendline(3), upscli_ssl(3), upscli_strerror(3), upscli_upserror(3)

Network UPS Tools						    05/31/2012						      UPSCLI_LIST_START(3)

Linux and UNIX Man Pages

upscli_get(3) [posix man page]

Check Out this Related Man Page