similar to: upsmon.conf::POWERDOWNFLAG

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

?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

?Hello everybody, I'm working on the "Use difftime for time comparison" bug (#313634). Charles directed me to the other one "Use monotonic clock for monitoring" attended to by Baruch; I believe that's very good idea, however I'd use a bit more encapsulated & general approach: 1/ I'd create an opaque timer type and its get/set/cmp/inc/dec etc interface

?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 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, 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 to all, i install nut and it's work perfectly but when i start upsmon i recive the message: POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string My upmon.conf contain: MONITOR myups@theseo 1 orion91 carlos81 master SHUTDOWNCMD "/sbin/shutdown -h +0" HOSTSYNC 15 POWERDOWNFLAG /etc/killpower FINALDELAY 5 My killpower scrit in /etc/killpower

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

Greetings.. Maybe someone could clear up a small confusion or uncertainty... Reading the various files I got the first impression that the file (??) that holds POWERDOWNFLAG variable would be either located in the /etc/killpower directory or (using the info from the RedHat scripts directory) the /etc/sysconfig.. but further reading and a bit of guess and by golly.. I'm now

I'm running NUT 2.6.3 on Debian wheezy [ with a 3.3.0 i686 kernel ] I've installed NUT via Debian APT [ package nut version 2.6.3-1 ] I have a REDi Blazer 600VA (BLAZER600c) UPS and I want to detect power failures. I have tried the following drivers: * gamatronic: Can't talk to UPS on port /dev/ttyS1! * bestups: Unable to detect a Best/SOLA or Phoenix protocol UPS * blazer_ser: No

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

Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > > both configurations are ok :). Please find the file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here:

Dear R users, The package proptest (http://www.davidkraus.net/proptest/) has been recently released to CRAN. The package provides functions for testing the proportional hazards assumption in the Cox model for right censored survival data. Two types of tests for identifying nonproportional covariates are implemented: * data-driven Neyman type smooth tests (using both nested and all-subsets

Hi, are this UPS supported by any other driver than "richcomm_usb". The device works with richcomm_usb, but only signals online, offline etc. Not voltage, batterylevels etc. Bus 006 Device 009: ID 0925:1234 Lakeview Research Bus 006 Device 009: ID 0925:1234 Lakeview Research Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10