Displaying 4 results from an estimated 4 matches for "upscli_add_host_cert".
2014 Jun 03
2
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
...ry_max = 13.6
This is how the things need to be specified, right?
In any event, I pulled the whole tree but its build fails as follows:
make[2]: Entering directory `/home/bruda/nut-master/docs/man'
Using existing upsclient.3 manual page, since 'asciidoc' was not found.
Using existing upscli_add_host_cert.3 manual page, since 'asciidoc' was not found.
Using existing upscli_cleanup.3 manual page, since 'asciidoc' was not found.
Using existing upscli_connect.3 manual page, since 'asciidoc' was not found.
Using existing upscli_disconnect.3 manual page, since 'asciidoc' w...
2014 Jun 03
0
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
...things need to be specified, right?
Yes.
> In any event, I pulled the whole tree but its build fails as follows:
>
> make[2]: Entering directory `/home/bruda/nut-master/docs/man'
> Using existing upsclient.3 manual page, since 'asciidoc' was not found.
> Using existing upscli_add_host_cert.3 manual page, since 'asciidoc' was not found.
> Using existing upscli_cleanup.3 manual page, since 'asciidoc' was not found.
> Using existing upscli_connect.3 manual page, since 'asciidoc' was not found.
> Using existing upscli_disconnect.3 manual page, since '...
2014 Jun 01
0
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
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
2014 May 24
3
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
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