search for: upscli_disconnect

...doc' 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' was not found. Using existing upscli_fd.3 manual page, since 'asciidoc' was not found. Using existing upscli_get.3 manual page, since 'asciidoc' was not found. Using existing upscli_init.3 manual page, since 'asciidoc' was not found. U...

...nd. > 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' was not found. > Using existing upscli_fd.3 manual page, since 'asciidoc' was not found. > Using existing upscli_get.3 manual page, since 'asciidoc' was not found. > Using existing upscli_init.3 manual page, since 'asciidoc' w...

Hello, I was running upsmon some time without UPS connected and noticed significant memory leak. After some debugging I found the leak source. It is in file clients/upsclient.c. Function upscli_connect() allocates memory for ups->pc_ctx and in case of any error, just returns -1 without freeing it. My NUT version is 2.2.0, but I quickly looked through 2.2.1 sources and it seems this bug was not

...+78,8 @@ > int upscli_splitname(const char *buf, char **upsname, char **hostname, > int *port); > > +int upscli_splitaddr(const char *buf, char **hostname, int *port); > + > int upscli_sslcert(UPSCONN *ups, const char *file, const char *path, int verify); > > int upscli_disconnect(UPSCONN *ups); > > _______________________________________________ > nut-commits mailing list > nut-commits@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-commits >

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

...ed 'readlen' upsclient.c:1383: error: 'UPSCONN_t' has no member named 'readidx' upsclient.c:1386: error: 'UPSCONN_t' has no member named 'readbuf' upsclient.c:1386: error: 'UPSCONN_t' has no member named 'readidx' upsclient.c: In function 'upscli_disconnect': upsclient.c:1515: error: 'UPSCONN_t' has no member named 'ssl' upsclient.c:1516: warning: implicit declaration of function 'PR_Shutdown' upsclient.c:1516: error: 'UPSCONN_t' has no member named 'ssl' upsclient.c:1516: error: 'PR_SHUTDOWN_BOTH' u...