similar to: 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:

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

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

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 >

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, 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

> I see. For IP4 addresses, will ups@192.168.0.1:3493 still work as > expected? -- Peter Yes. Whatever is between '@' and the optional ':<portnumber>' is passed as hostname. Brackets (in case of domain literals) are removed. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57

> I see. For IP4 addresses, will ups@192.168.0.1:3493 still work as expected? -- Peter Yes. Whatever is between '@' and the optional ':<portnumber>' is passed as hostname. Brackets (in case of domain literals) are removed. One thing to note, in the released versions the use of IPv4 addresses for a hostname (in upsclient.c) is not guaranteed to work (according to POSIX):

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.

tags 439986 upstream thanks Hi Florian, 2007/8/29, Florian Forster <octo at verplant.org>: > Package: nut-dev > Version: 2.2.0-1 > Severity: minor > > After upgrading from version 2.0.something to version 2.2.0-1 the type > `UPSCONN' had been renamed to `UPSCONN_t'. This is a problem for > software that is supposed to work with different versions of this >

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

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

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'

I'm trying to use the IAPWS95 package with the tidyverse packages. For some reason, the function is not outputting the correct rho. A minimal example with results is below. I've also included the definition of the DTp function from the IAPWS95 library. ==================================== library(IAPWS95) library(tidyverse) initial <- data.frame(T=c(279,294),p=c(0.46,0.46))

Hi Shawn, I don't think it has anything to do with the tidyverse. If you keep simplifying your example you'll get all the way down to > DTp(T=c(279,294),p=c(0.46,0.46)) [1] 1000.12283 --Ista On Wed, May 30, 2018 at 2:14 PM, Shawn Way <SWay at meco.com> wrote: > I'm trying to use the IAPWS95 package with the tidyverse packages. For some reason, the function is not

Hello, No ttyUSB* device under /dev however the new driver has detected the UPS, the nut services are able to start, just "upsc -l ups" sais unknown error and doesn't return any information. Could be due to the driver unable to detect number of battery packs as reported by the nut-driver.service startup? How can I fix that? root at omv:~# systemctl status nut-driver.service●

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

Although the bug in Samba 1.9.17p1 which caused "ERROR: set_share_mode: failed to ftruncate share mode file" messages in log.smb has been fixed in 1.9.17p2, empty share* files are not being deleted from the lock file directory. Regards, Tim > Tim Boorman > UNIX Systems Support > Lusis Limited, Technology Drive, Bridgend Science Park, Bridgend, > United Kingdom CF31 3UJ

-- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 > Is there any reason we don't just do serial PnP? Do UPSes not generally support this? Unfortunately, many cheap ones don't or have implementation flaws (the Sweex 1000 for instance, which calculates the CRC in the wrong way). In fact, there are a fair number of UPSes in the list of