similar to: NUT IPC module of libnutconf pushed

Displaying 20 results from an estimated 300 matches similar to: "NUT IPC module of libnutconf pushed"

2012 Dec 11
0
libnutconf: Basic UTs for libnutconf pushed
?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
2012 Dec 10
0
libnutconf: An overview
?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
2012 Dec 07
0
libnutconf: (De)serialisation methods added
?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
2012 Dec 04
1
libnutconf: specific C++ accessors technique 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
2012 Nov 28
1
upsmon.conf::POWERDOWNFLAG
?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,
2012 Oct 10
1
upsmon twin-daemon?
?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
2012 Oct 08
1
HPUX warning during build spotted
?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
2012 Dec 10
0
UPP schedule and progress
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
2013 Apr 18
0
Nut-upsuser Digest, Vol 94, Issue 18
?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
2012 Sep 27
3
NUT Bugs #313634 & #313714: unification & encapsulation of timer proposition
?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
2012 Oct 29
1
Nut-upsdev Digest, Vol 88, Issue 22
?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 Oct 16
2
nut_clock_* unit test ideas
?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;
2012 Sep 05
2
[nut] High level C and C++ libnutclient (#2)
[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
2014 Sep 30
0
C++ in NUT
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
2012 Oct 09
1
network-ups-tools won't shutdown my PC
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
2013 Apr 26
1
[nut] usbhid-ups: trailing spaces in nut-scanner output not ignored when trying to find ups (#26)
On Apr 25, 2013, at 9:42 AM, Christian Wiese wrote: > I created a pull request #27 which is fixing the issue. > > # nut-scanner -qNU > [nutdev1] > driver = "usbhid-ups" > port = "auto" > vendorid = "051D" > productid = "0002" > product = "Back-UPS ES 700G FW:871.O2 .I USB FW:O2" > serial = "5B1243T01934"
2007 Feb 26
2
fs quota - what I am doing wrong?
Hi everyone, on my server, i have quota set on /home partition (ext3). mount says: root at zen:/var/log# mount |grep quo /dev/sda8 on /home type ext3 (rw,noatime,usrquota) /dev/sda7 on /tmp type ext3 (rw,noatime,usrquota,data=writeback) System is debian/stable (distribution 2.6.8-3-686-smp kernel), quotas are working: root at zen:/var/log# quota ax Disk quotas for user ax (uid 506):
2013 Feb 06
1
Alioth Subversion repository freeze
Dear developers, thanks to Charles (Lepple) and ESR hard work, we are now able to finalize our migration from Subversion to Git, on Alioth. As of now, our Subversion repository on Alioth<https://alioth.debian.org/scm/?group_id=30602>is FROZEN! Any new svn commit may simply be discarded, so beware! Most active developers are currently using github, as a temporary mean. But if you have any
2012 Oct 12
0
NUT drivers socket polling issues
Hello gents, while getting rid of gettimeofday, I've spotted something I'd like to discuss in implementation of socket polling in driver/main.c::main and driver/dstate.c::dstate_poll_fds My observations follow: 1/ I'm not very happy with the poll mechanism design as whole. I mean, typically, you implement the poll as { poll(); process(); }* loop; in pseudo-code: shut_down = false;
2012 Nov 09
1
nut_clock_* UT review
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