search for: upscli_sendlin

...doc' was not found. Using existing upscli_list_next.3 manual page, since 'asciidoc' was not found. Using existing upscli_list_start.3 manual page, since 'asciidoc' was not found. Using existing upscli_readline.3 manual page, since 'asciidoc' was not found. Using existing upscli_sendline.3 manual page, since 'asciidoc' was not found. Using existing upscli_splitaddr.3 manual page, since 'asciidoc' was not found. Using existing upscli_splitname.3 manual page, since 'asciidoc' was not found. Using existing upscli_ssl.3 manual page, since 'asciidoc' was...

...nd. > Using existing upscli_list_next.3 manual page, since 'asciidoc' was not found. > Using existing upscli_list_start.3 manual page, since 'asciidoc' was not found. > Using existing upscli_readline.3 manual page, since 'asciidoc' was not found. > Using existing upscli_sendline.3 manual page, since 'asciidoc' was not found. > Using existing upscli_splitaddr.3 manual page, since 'asciidoc' was not found. > Using existing upscli_splitname.3 manual page, since 'asciidoc' was not found. > Using existing upscli_ssl.3 manual page, since 'as...

...; messages every five seconds. I cannot seem to find a way to reduce that chatter. These messages originate in pollups() in clients/upsmon.c. It looks to me like pollups() sees the utype_t->status flag ST_CONNECTED set, yet the UPSCONN_t->fd is -1, which means there is no valid connection (upscli_sendline() in clients/upsclient.c sets UPSCONN_t->upserror = UPSCLI_ERR_DRVNOTCONN). If ST_CONNECTED was clear, the connection would be retried. It appears to me that because ST_CONNECTED is set, pollups() thinks it should have a good connection and is surprised to find out it does not. Thus, it alwa...

On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> Don't worry about the battery physical properties for now - the >> problem there is that we don't have enough information from the UPS >> to do a proper calculation. With the V_interval[] settings, you can >> tweak the new state-of-charge calculation to match what you see via >> upsc when the battery is

Hello, At 09:24 -0400 on 2014-5-23 Charles Lepple wrote: > > See attached. Still doesn't have the writable V_interval values, > but I probably won't have time to test that until later. Thank you for the patch. > Don't worry about the battery physical properties for now - the > problem there is that we don't have enough information from the UPS > to do a