similar to: libnutconf: (De)serialisation methods added

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

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

[I took the liberty of replying on nut-upsdev - not many people are using github yet since the NUT repository native format is still SVN.] On Sep 4, 2012, at 10:17 AM, Emilien Kia wrote: > This is a proposal for a new client library which scopes an higher level than the existing libupsclient. > > It needs less dependencies to be compiled than the libupsclient and can be easier to

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

I have seen a lot of recent posts about building on AIX 5.2, 5.3, etc. but none showed the same problems I am having. After building Samba 3.0.21b on AIX 5.2, I get this error when running a number of the binaries: > ./testparm exec(): 0509-036 Cannot load program ./testparm because of the following errors: 0509-130 Symbol resolution failed for /usr/lib/libc.a(posix_aio.o) because:

On Aug 14, 2012, at 2:05 PM, Steve Montgomery <stephen.montgomery3 at btinternet.com> wrote: > Further to my earlier question, I'm perhaps a bit confused about memory serialisation. The following example, compiled using clang for the MSP430: > > target datalayout = "e-p:16:16:16-i8:8:8-i16:16:16-i32:16:32-n8:16" > target triple = "msp430-??-??" >

the case: i have two classes: 1) class Contract < ActiveRecord::Base serialize :addons end 2) class Addon < ActiveRecord::Base end Now i do the following in contract_controller: def create @contract = Contract.new(params[:contract]) @contract.user_id = session[:user_id] @contract.customer_id = params[:customer_id] @contract.pending = 1 @contract.addons = Array.new end def update

> No, a chain is supposed to mean "later than". It sounds like MSP430 is bending > the rules here. The instruction selector for ADD16mm is autogenerated, so, this is not MSP430 bug alone :) This is just the single target in the tree which has mem-mem instructions. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

I posted to llvmdev a few months ago to ask for advice on the best way to avoid the SelectionDAGBuilder from imposing a constraint whereby a volatile load would be serialised relative to all pending loads. The LLVM LRM says that a volatile load only needs to be serialised relative to other volatile loads and, while it may not matter to most targets, the current behaviour of the SelectionDAGBuilder

----- Original Message ----- From: jorma.heikkuri@metso.com To: jojowil@samba.org Sent: Friday, October 06, 2006 8:24 AM Subject: Samba 3.0.23c and libiconv on AIX 5.3 Hello, I Installed your packages to new AIX 5.3 TL 5 server from: http://us3.samba.org/samba/ftp/Binary_Packages/AIX/ gunzip opt-samba-base.tar.gz opt-samba-3.0.23c-AIX5.tar.gz When I start nmbd I

The use of C++ has cropped up from time to time in the Github comments, and it really deserves its own thread. Background: https://github.com/networkupstools/nut/issues/102 From Arnaud: > @clepple : also a separate discussion, but quickly: c++ is more for devs than users. Though, by side effect, this will obviously benefit to the user, the point is to have better code (and coding) for some