search for: nutstream

...ted by Emilien K. some months ago; during the last month or so, I continued on the implementation, culminating these days by announcing that the core is basically coded. The library now contains an I/O layer, allowing synchronous access to configuration data (stream) in memory, file and on socket: nutstream module. There is a number of configuration classes associated with the following configuration files: nut.conf, upsmon.conf, upsd.conf, ups.conf and upsd.users (hope I didn't forget any). Support for these we need, right now; upssched.conf support will be added, later. The config. containers a...

...art of the NUT framework, either. I suggest libnutipc. Ext. commands execution (i.e. basis for driver inst. update): The core is already implemented at least in the nut_clock_* iface UT; it should be quite easy to make use of it. 2/ Sending signal to other process is a pretty simple task and with NutStream, we can read PIDs from .pid files on a couple lines of code... If it's implemented in libnutipc, we shall have to factorise libnutconf, though (extract nutstream). I suggest libnutio. 3/ Config. attribute access: As suggested for the nutconf tool, the access from command-line shall be done vi...

...4c7fef71741b33bff11a482a103360250e 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 it's enough for now, but in the future, the parser should be modified to use NutStream, directly. Nevertheless, this means that the code responsible for reading/writing nut.conf, upsmon.conf, upsd.conf, ups.conf and upsd.users and assembly of the associated configuration objects is there. Note however, that most of the code wasn't U-tested, yet. I wanted to write UTs, today, bu...