similar to: NUT Bugs #313634 & #313714: unification & encapsulation of timer proposition

?Hello fellow developers, yesterday, I was thinking about how to implement specific config. attributes accessors in section-based nut config. files so that it's nice to use and consistent with NutConfiguration, UpsmonConfiguration and UpsdConfiguration config. classes (where it's done via Settable attributes). The GenericConfiguration class provides generic access to name/value items of

?Hello Arnaud, Charles, regarding the nut_clock_* iface unit testing, I came to the following conclusion: 1/ It is IMO generally impossible to do deterministic unit test; the problem in question is inherently non-deterministic (I mean non-det. by nature). Justification: the main reason is that we can't perfectly predict the CPU time spent on computation, mainly because we have multi-tasking;

?Hello everybody, I've just noticed that POWERDOWNFLAG defaults to /etc/killpower in upsmon.conf. I believe that such files belong to the /run sub-tree. Not only because it's not a config. file; mainly because many embedded systems actually have most of the FS read-only and have only the /tmp, /var and /run writable... Is there any particular reason to keep the file in /etc? Thanks,

?Hello gents, I just have a quick question: yesterday, I was doing some UTing with upsmon and I've noticed that I always get 2 upsmon daemons; is that intentional? Why? Thanks, vasek -- V?clav Krpec Software Developer Network UPS Tools project Eaton Opensource Team Eaton European Innovation Center ----------------------------- Eaton Elektrotechnika s.r.o. ~ S?dlo spolecnosti, jak je

?Hello everybody, during the last build (#380) on HPUX (eaton-hpux11-pa-risc buildslave), I've noticed the following warning when compiling upsd: ../../server/upsd.c:417: warning: implicit declaration of function 'fromhost' fromhost is either an alias for sock_host or declared as extern void fromhost() in tcpd.h (iff any of TLI or PTX or TLI_SEQUENT macra are defined), which I guess

Hello, I'm using Archlinux x86_64 with linux-nouveau kernel (based on linux-mainline (that is linux-3.6)). I've installed nut-2.6.5. I first tried to use new systemctl .service scripts, but they are problematic. So I start and stop nut from /etc/rc.c script. This way, it "woks". Here are my config files : nut.conf : MODE=netserver ups.conf : [ellipse] driver = usbhid-ups

?Hello Sabine, this seems as a problem with PATH env. variable; if you issue the command by hand, you do so in an environment with PATH set so that the binaries are found. I guess that the nut user doesn't have so nice PATH, being non-interactive. Try to add full paths to your binaries in the command and see what happens... Regards, vasek -- Vaclav Krpec NUT developer

?Hello everybody, just a few notes to the doxygen X man issue: 1/ AFAIK doxygen can generate man pages, so why don't we just generate them and decide then whether they are ill fitted or usable... 2/ I'd definitely use doxygen when possible; I mean I don't know any alternative that's able to do (at least partial) validation of the documentation with the source 3/ I

2012/11/9 <VaclavKrpec at eaton.com> > Hello gentlemen, > Hi Vasek, I'm moving the thread to -upsdev, since it has not to be private... please note that revisions 3771 and 3772 conclude nut_clock_* > development (including UTs): > interestingly enough, we were talking about that 5 mn ago with Emilien ;) my conclusion was that nut_clock devs were completed with 3772, and

?Hello everybody, basic UTs for libnutconf were pushed to balooloo/nut, libconf branch: https://github.com/balooloo/nut/commit/f453459419abf6c597d5d186494f91ed6f0e81aa Note that the tests are not exhaustive; however, they test the most prominent (sample) configuration settings (de)serialisation. The code should also give you an idea about how to write a simple configuration manipulation program

?Hello everybody, (de)serialisation methods of all the currently existing config. classes were pushed to balooloo/nut, libconf branch: https://github.com/balooloo/nut/commit/df8b584c7fef71741b33bff11a482a103360250e Please note that the deserialisation methods should work, however they are quite inefficient since they simply read the whole stream to memory and then call parseFromString. I guess

?Hello everybody, 1st (and yet incomplete) version of IPC support module for libnutconf was pushed: https://github.com/balooloo/nut/commit/0fbf351b5ee9899bd89cf17314727c69c2d5471c The code contains lots TODO; I commit it mainly because I'll be off on holiday for some time, so you may review and I might perhaps work on it a little bit if I get extremely bored... ;-) As always, any comments,

?Hello fellow developers, as you may have noticed from a few e-mails in the past, there is a new NUT library in development these days. It should be part of the NUT platform API in the future and I'd like to present the status of work, hereby. 1/ The library shall be responsible of NUT configuration management. It shall encapsulate access and manipulation with all the configuration

For reference: https://github.com/networkupstools/nut/issues/10 On Mar 5, 2015, at 1:09 AM, Baruch Even <baruch at ev-en.org> wrote: > Hi, > > There is one issue that I would consider as a major issue and not fixed yet. It is the use of wall time for scheduling ups polls instead of a monotonic clock source. I provided a (partial) patch in the past and I believe there was some

Vaclav, NUT is failing to build on OS X 10.6 and 10.7 With GCC/g++: http://buildbot.networkupstools.org/public/nut/builders/MacOSX-10.6-x86/builds/340/steps/compile/logs/stdio The same branch with clang/clang++: /bin/sh ../libtool --tag=CXX --mode=compile clang++ -DHAVE_CONFIG_H -I. -I../include -I../include -g -O2 -MT nutipc.lo -MD -MP -MF .deps/nutipc.Tpo -c -o nutipc.lo nutipc.cpp

Hello everybody, so, here's the summary of my progress (note that it also includes a few items to discuss, so I'm cc-ing this to nut-upsdev as well). I. The planning: 1/ libnutconf: The core (i.e. config. classes and their (de)serialisers) is coded, UT in progress. Signalisation shall follow; I have a couple of practical thoughts & comments to this, see below. In general, I'd

Hi, There is one issue that I would consider as a major issue and not fixed yet. It is the use of wall time for scheduling ups polls instead of a monotonic clock source. I provided a (partial) patch in the past and I believe there was some work on it. The bug manifests itself as a stop of monitoring with no alarm when the clock is moved backwards in time. Please consider adding this to the

We only have a few open items that I think should be resolved before releasing 2.7.3. The list grew a bit in the past week, but we'll cover that later. Here is the list: * #93: Devices Dumps Library improvements <https://github.com/networkupstools/nut/issues/93> * #158: Powerware BCMXCP advanced features <https://github.com/networkupstools/nut/pull/158> * #185: insecure storage

Hi, I've submitted a patch to the Alioth tracker but thought to give a heads up here as well, I have an issue with nut not working when the clock is moved backwards. I provided a patch[1] to use clock_gettime with CLOCK_MONOTONIC to fix this, based on comments from Charles Lepple I made a few changes and it can be seen in a git branch I created at [2]. Let me know what you think. Baruch

Sadly, I'm back with another issue. I can do a "system list --all" just fine; however, if I attempt to start the machines, I get back: maas@Bill-MAAS-cc:~$ strace -s 1024 -f -o /tmp/asdfasdf.log virsh -c vbox+ssh://gbadmin@10.20.0.1/system start PXE-client-07 error: Failed to start domain PXE-client-07 error: An error occurred, but the cause is unknown Log files on both client