similar to: upscli_splitname() for upsc_list (was: Re: 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

I finally got some time to implement a pair of options to upsc for listing all configured UPSes on a given upsd: http://boxster.ghz.cc/projects/nut/changeset?new=branches%2Fupsc_list%2Fclients%2Fupsc.c%40859&old=trunk%2Fclients%2Fupsc.c%40821 http://boxster.ghz.cc/projects/nut/browser/branches/upsc_list/clients/upsc.c?rev=859 I think this should work with the new functions for parsing IPv6

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

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:

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

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

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

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

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

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

Until the release of nut-2.0.5 it was possible to have a working configuration without configuring anything in 'ups.conf'. Since then, this no longer works, as the server will only look for driver sockets for UPSes that have been configured in 'ups.conf' (since the socket is named after the UPSname). Drivers will use the old naming scheme '<driver>-<port>' if

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT

Hi Bj?rn, 2009/10/9 Bj?rn Torkelsson > Public bug reported: > > Binary package hint: nut > > I have recently upgraded from hardy to intrepid to jaunty. After > upgrading to Intrepid the megatec_usb stopped recognizing my Trust PW- > 4130M ups, it still does not work on Jaunty. It worked without any > problems in hardy. > > I tried the megatec_usb driver from hardy

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)

Hi, Great work Jim! I?m glad you could reproduce the problem and found a potential culprit. Just for my own interest I restored upsshed from my backups (version 2.7.4-13) and it seems to running ok, so no big runtime changes regarding that with Debian 12. It is not hogging CPU. From the daemon log the heartbeat seems to be working ok. Only difference between the old logs (pre Debian 12 update)

Hello guys Yesterday i started do configure my Mustek Powermust650 with nut using the megatec_usb driver. Everything works fine except for the mailing when something happens. My upsmon looks like this: MONITOR powermust650 at localhost 1 local controller master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /root/upsmailer POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15

> On Aug 13, 2018, at 06:17, Charles Lepple <clepple at gmail.com> wrote: > > On Aug 12, 2018, at 11:03 PM, Kevin Mychal M. Ong <kevindd992002 at yahoo.com> wrote: >> >> Hi, >> >> I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT