similar to: libnutconf: An overview

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

2012/10/12 Emilien Kia <kiae.dev at gmail.com> > Hi guys, > Hi Emilien and the list, This is a pull request to finally merge NSS feature in nut trunk: > https://github.com/clepple/nut/pull/3 > I'd like to take a moment to shed some more light on this important development, which lasted 3 years: - the initial

?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

On Apr 8, 2015, at 9:44 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > - #190: upsd: NSS SSL only working in debug mode => NEED TESTING before merging > Emilien has made a fix and PR (#199: Initialize SSL after deamonize and downgrade to user.) > The user (Melkor Lord) has ack'ed the fix. > The fix is indeed trivial but I want to ensure that there is no

Hi Charles and the list here is an update on 2.7.3 2015-03-20 3:33 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 19, 2015, at 2:00 PM, Arnaud Quette <arnaud.quette at gmail.com> > wrote: > > * #158: the branch has been collapsed into one commit, but additional >> documentation (nut-names.txt) is needed: >>

Hi Charles, 2015-04-11 21:22 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Apr 8, 2015, at 9:44 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > > - #190: upsd: NSS SSL only working in debug mode => NEED TESTING before > merging > Emilien has made a fix and PR (#199: Initialize SSL after deamonize and > downgrade to user.) > The user (Melkor

2015-04-27 15:02 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Apr 27, 2015, at 2:48 AM, Nick Ma. <nick.mayerhofer at enchant.at> wrote: > > > But it still doesn't compile any executable: ~/nut/tests% ls > > cpputest.cpp example.cpp Makefile Makefile.am Makefile.in > > I think it is only intended to produce an executable when running "make

Some precisions: we are not alone, some projects had similar problem: http://bugs.bitlbee.org/bitlbee/ticket/785 And the problem is really coming from NSS initialization. Discussion about the issue here : http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html There is a workaround to use NSS with fork but it is more setting a flag to share some resources (primarily sockets) but must

2015-03-26 9:03 GMT+01:00 Arnaud Quette <arnaud.quette at gmail.com>: > Hey mister M' > > A first huge thanks for taking care of this, and so late in the night. I > know that it's not easy... > > (sent from my S3... please excuse my brevity) > Le 25 mars 2015 18:49, "Emilien Kia" <kiae.dev at gmail.com> a ?crit : > > > > > >

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:

Dear fellows, As you have probably seen, NUT has had a recent boost through the help of Eaton. Frederic Bohe (contractor for Eaton France) has worked on Augeas, and is now working the Windows port. Chetan Agarwal, seconded by Prashi Gandi (both from Eaton India) are working on XCP and quality / validation related projects. I'm now pleased to announce that Emilien Kia (contractor for Eaton

Hey mister M' A first huge thanks for taking care of this, and so late in the night. I know that it's not easy... (sent from my S3... please excuse my brevity) Le 25 mars 2015 18:49, "Emilien Kia" <kiae.dev at gmail.com> a ?crit : > > > > 2015-03-21 17:06 GMT+01:00 Melkor Lord <melkor.lord at gmail.com>: >> >> >> On Fri, Mar 20, 2015

Hello all, I come back to request comments (and merge) on my pull request of the libnutclient. https://github.com/clepple/nut/pull/2 All previous comments have been addressed (some fixes and documentation). For memory, the libnutclient is an high-level C++ and C client library allowing to dialog with upsd. The addressed model is oriented around devices, variables and commands; unlike

2015-03-21 17:06 GMT+01:00 Melkor Lord <melkor.lord at gmail.com>: > > On Fri, Mar 20, 2015 at 4:40 PM, Emilien Kia <kiae.dev at gmail.com> wrote: > > Some precisions: >> >> we are not alone, some projects had similar problem: >> http://bugs.bitlbee.org/bitlbee/ticket/785 >> And the problem is really coming from NSS initialization. Discussion

Cheers all, A recent discussion in the issue tracker brought up the idea to allow the `LISTEN` keyword to also accept a single "host:port" token (e.g. if there is only one argument, with at least one colon, and the last colon is followed only by numbers, split it into host and port) : https://github.com/networkupstools/nut/issues/2424 I see certain pros to the idea (may be more

Cheers all, A recent discussion in the issue tracker brought up the idea to allow the `LISTEN` keyword to also accept a single "host:port" token (e.g. if there is only one argument, with at least one colon, and the last colon is followed only by numbers, split it into host and port) : https://github.com/networkupstools/nut/issues/2424 I see certain pros to the idea (may be more