similar to: Memory leak in upsmon

Displaying 20 results from an estimated 400 matches similar to: "Memory leak in upsmon"

2014 Jun 03
2
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
Hello, At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: > > 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
2014 Jun 03
0
Tripp Lite SMART3000RM2U (protocol 3003) running time and charge?
On Jun 2, 2014, at 10:25 PM, Stefan Bruda wrote: > Hello, > > At 15:42 -0400 on 2014-6-1 Charles Lepple wrote: >> >> 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
2007 Jan 23
2
Re: [nut-commits] svn commit r731
Hi Arjen, in server/upsd.c r731, you moved the call conf_load() from after check_perms() (~ l.1020) to before setupsignals() (~ l.989). The problem is that conf_load() needs to open the ups driver socket, and it assumes that STATEPATH is the current working directory. The directory is only set in l.1016. Therefore, the first attempt to open a socket will always fail. From the user's point of
2007 Jan 06
3
Re: [nut-commits] svn commit r708 - in trunk: . clients server
With the Ipv6 patch (r708), I get: upsclient.c: In function `upscli_connect': upsclient.c:469: `AI_ADDRCONFIG' undeclared (first use in this function) upsclient.c:469: (Each undeclared identifier is reported only once upsclient.c:469: for each function it appears in.) Even if it doesn't break IPv4 support, it may break portability, as IPv6 seems to require specific functions that are
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
2007 Jan 13
3
Default NUT PORT
In my latest patch, I hardcoded the port NUT uses for TCP communication (3493). The reason is, that I can't figure out a way how to change the numeric value of the #define'd PORT into a character string. Using snprintf() and a temporary buffer just seems wrong, since this should be handled by the preprocessor, rather than at runtime. The following files are affected: - server/conf.c (line
2011 Jun 28
3
Changes to upscli_connect
Hello, I am currently working on the nut scanner. For detecting available upsd on the network, I rely on upscli_connect. The problem with this function is that it calls a blocking "connect" function. So the nut-scanner is blocked while waiting for the TCP timeout when trying to connect to an IP without upsd available . Since this timeout may be rather long (3 minutes on my host), I
2007 Jan 19
1
Re: [nut-commits] svn commit r755 - in trunk: . clients
Great, thanks! Two questions: * what is a domain literal? Is this something like 192.168.0.1? In this case, the '[]' are probably unnecessary. * are you sure you want to use fprintf(stderr, ...) in a library? This doesn't seem like a good idea to me. Wouldn't it be more consistent to extend upscli_errlist[] ? -- Peter Arjen de Korte wrote: > > Author:
2007 Jan 06
1
Re: [nut-commits] svn commit r710 - in trunk: . clients server
Great, thanks Arjen! Now we need an autoconf test to set HAVE_IPV6 automatically. I will look into what functionality needs to be tested; the test can be refined as problems arise later. -- Peter Arjen de Korte wrote: > > Author: adkorte-guest > Date: Sat Jan 6 19:39:08 2007 > New Revision: 710 > > Modified: > trunk/ChangeLog > trunk/clients/upsc.c >
2015 Feb 13
1
Error installing Nut 2.7.2 on RedHat 6.6
Hi, I need help because I can't install Nut in RedHat EL 6.6 The version of Nut in repository ot RHEL is 2.6.5-2, but doesn't suppor my UPS, Liebert GXT3-200RT. I read that it is supported using Nut version 2.7.2, but I looking all around the web how to install it in my RedHat but I didn't find answers. Follow the guide, I can downlad lasted version stable on web: 2.7.2 Here the
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
2007 Jan 14
1
upscli_splitname() for upsc_list (was: Re: Default NUT PORT)
On 1/13/07, Peter Selinger <selinger@mathstat.dal.ca> wrote: > > The question is when exactly this should be converted to a number. > > Should this be done in upscli_splitname() or in upscli_connect()? The > > latter would require a change in the prototypes of upscli_splitname() > > and upscli_connect(), and an attendant change in all the existing > > clients.
2015 Oct 19
0
upsmon Poll UPS "Driver not connected" messages
I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I am testing implementation of NUT features with APC and Tripp-Lite USB UPS interfaces. Things are going reasonably well. However, I'm seeing many more messages than I would like in /var/log/messages when I boot the system without the UPS connected. I have configured NOCOMMWARNTIME 3600, which takes care to only broadcast
2007 Jan 12
2
Makefiles driving me NUTs
I want to use upsdebugx, upslogx in 'clients/upsclient.c', however this fails with the following error messages (I trimmed the path to the build directory to <path> in order to prevent line wrapping): <path>/clients/upsclient.c:941: undefined reference to `upsdebugx' <path>/clients/upsclient.c:910: undefined reference to `upslogx'
2007 Nov 06
1
Powerware PW5115 USB driver
Hi I have PW 5115 500 UPS which has both RS232 and USB connectors. bcmxcp driver works fine with serial connection but bcmxcp_usb does not with USB one. After some USB sniffing on windows box I've found that PW5115 communicates in other way than supposed in driver. Applying attached patch makes driver to work properly. System: FreeBSD 6.2 but ugen driver needs patching in order to respect
2018 Jul 12
0
2.7.4 uses deprecated back level of TLS
2.7.4 explicitly calls for use of a deprecated back level of TLS. On Debian stretch, after ./configure --with-openssl, make produces the following warning: upsclient.c: In function 'upscli_init': upsclient.c:322:2: warning: 'TLSv1_client_method' is deprecated [-Wdeprecated-declarations] ssl_method = TLSv1_client_method();
2007 Mar 12
1
infinite loop in clients/upsclient.c connect
I was testing some code for listing available UPSes, and when I tried connecting to a machine that didn't have upsd running, upsc went into an infinite loop on OS X (IPv6 enabled). The error code returned by connect is EINVAL, which apparently isn't one of the errors documented in connect(2) here. http://boxster.ghz.cc/projects/nut/changeset/731
2008 Aug 15
2
Problem with APC and Fedora 8 I86_64
I have been trying to get Nut working on a system with Fedora 8 i86_64 installed and an APC Smart-UPS USB. The 2.2.0 rpm does not seem to like the USB on this UPS. I have tried compiling the 2.2.2 version, from source, but am getting warnings. I have tried building it on my i386 system (f8 as well) and I get no warnings also the 2.2.0 works fine on that one with a TrippLite Omni 900 LCD via
2008 Jul 17
0
r1515 - branches/trunk-make-package: anybody interested in taking over?
Hi, I've taken a small bit of time to initiate this work. There is now: - an m4 macro to detect the system (linux only ATM, but simple to complete) - a set of "make package" targets throughout the tree (limited to debian ATM) The remaining tasks on this specific point are: - m4 macro completion to handle all the supported platforms (at least the ones that have files in the
2011 Jul 06
4
upsclient high level API and Java wrapping
Hi all, on proposal by Arnaud Quette and sponsored by Eaton, I will work on a port on Java of client, discovery and config API. As I have already suggested (mail of 2011-06-14 of this ml), instead of developping another port of nut protocol, I suggest to develop a higher level API in C/C++ uppon existing upsclient, inspirated by existing C-based tools and python and perl rewrites. The second