search for: upscli_strerror

...t seem like a good idea to me. Wouldn't it be more > consistent to extend upscli_errlist[] ? Errorcodes are passed in 'ups->upserror' (and 'ups->syserrno'). Uh oh, we don't have a connection to an UPS yet when we call upscli_splitname() or upscli_splitaddr(). The upscli_strerror() function that is used to return the message in upscli_errlist[] needs a pointer to a UPSCONN structure also. The upscli_errlist[] is static, so there is no way to get to the messages without calling upscli_strerror(). The reality is, that this is how it has been for a *very* long time, I didn...

...;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 not found. Using existing upscli_strerror.3 manual page, since 'asciidoc' was not found. Using existing upscli_upserror.3 manual page, since 'asciidoc' was not found. Using existing libnutclient.3 manual page, since 'asciidoc' was not found. Using existing libnutclient_commands.3 manual page, since 'asciidoc'...

...ot 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 not found. > Using existing upscli_strerror.3 manual page, since 'asciidoc' was not found. > Using existing upscli_upserror.3 manual page, since 'asciidoc' was not found. > Using existing libnutclient.3 manual page, since 'asciidoc' was not found. > Using existing libnutclient_commands.3 manual page, since ...

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

...39;upscli_cleanup': upsclient.c:445: warning: implicit declaration of function 'NSS_Shutdown' upsclient.c:446: warning: implicit declaration of function 'PR_Cleanup' upsclient.c:451: warning: implicit declaration of function 'PL_ArenaFinish' upsclient.c: In function 'upscli_strerror': upsclient.c:502: warning: implicit declaration of function 'PR_GetErrorTextLength' upsclient.c:503: warning: implicit declaration of function 'PR_GetErrorText' upsclient.c: In function 'net_read': upsclient.c:560: error: 'UPSCONN_t' has no member named 'ssl...