similar to: Changes to upscli_connect

Built for years every version using: ./configure --with-usb Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: yes build neon based XML driver: yes build Powerman PDU client driver: no build IPMI driver: no enable SSL development code: yes enable libwrap (tcp-wrappers) support: yes build CGI programs: no enable HAL support: no

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.

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

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

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

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

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

2012/3/23 Vladi Belperchinov-Shabanski <cade at datamax.bg> > > hello, > Hi, I'm adding -upsuser list for info > from the source documentation I figured you are dev coordinator. > I'm sorry if I got it wrong and please forward to the correct person > if possible, thanks! > I'm indeed leading NUT, but the preferred support way is through the mailing

Jim Klimov via Nut-upsuser writes: > So... determining that FD is to be reaped proved hard. Internet lore suggests > fcntl() and poll() on the FD, but it just seems valid to them. The errno is > also usually not raised (once I saw a "111: Connection refused" though). > So the best dumb idea so far is to bail out if we spent the whole loop (128 > attempts) and only

2011/6/27 Frederic BOHE <fbohe-guest at alioth.debian.org> > Author: fbohe-guest > Date: Mon Jun 27 13:56:51 2011 > New Revision: 3060 > URL: http://trac.networkupstools.org/projects/nut/changeset/3060 > > Log: > Add NUT server scan. > > (...) > device_t * scan_snmp(char * start_ip, char * stop_ip,long usec_timeout, > snmp_security_t * sec); > >

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

One disadvantage of handling it through a script is that is will not be done by default. Most users probably don't know about the problem of burning batteries, as it is not very common. A potential problem with Eric Wilde's patch is that it is not general enough; some UPS models have an boolean OVERHEAT flag although they don't report the actual temperature. So the UPSOVERTEMP

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-3.msi This fixes a regression about stopping the NUT service. Feedback is highly appreciated. Regards, Fred -- Eaton Opensource Team - http://opensource.eaton.com ----------------------------- -----------------------------

Hello NUT Team! I continue playing with NUT for Windows and USBHID-UPS driver I've got from Frederic to fix "Data Stale" problem. It seems there is something wrong when Network UPS Tools service is starting with disconnected USB cable. UPSMON is writing "Data Stale" to output and continue do it infinitely, even the cable is connected back. Here is a short log: Network

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 >

Hi all, We are having a an ongoing problem with out NTLM authentication on out squid system. The problem tends to arise when users change their passwords. I have read a KB article that says that DC's will still continue to authenticate Old password for an hour or so after the password is changed. But I think it is between IE and winbindd that is the problem. Below is a trace at debug

Hello, I have been following the details in this article to configure my UPS: http://rogerprice.org/NUT.html However the system won't shutdown although file permissions look ok: ls -alF /usr/sbin/ups* -rwxr--r-- 1 upsd daemon 64984 Oct 15 2014 /usr/sbin/upsd* -rwxr--r-- 1 upsd daemon 48584 Oct 15 2014 /usr/sbin/upsmon* -rwxr--r-- 1 upsd daemon 31536 Oct 15 2014 /usr/sbin/upssched*

Hi, I have an OEM of KStar UDC9101S which is Megatec protocol rs232 capable unit. So I use blazer_ser protocol=megatec /dev/ttyUSB0 with no issue to get NUT running. Please direct me what command should I issue to collect the data in order to include the UPS to device database? P.S. tryed /lib/nut/blazer_ser -DD... but no difference from a regular output has being added by the driver.

I have a Dell PE 2850 connected via 940-0024C cable to serial port on the UPS mentioned above. I've used apt-get to install nut-2.0.2-3 and attempted to configure based on the documentation. So far I'm getting the following when I try to start ups daemon: server:/etc/ups # /etc/init.d/ups start Starting service NUT: -> Starting UPS driver: Network UPS Tools - UPS driver controller