search for: upscli_upserror

...9;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' was not found. Using existing libnutclient_devices.3 manual page, since 'asciido...

...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' was not found. > Using existing libnutclient_devices.3 manual page, sin...

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