similar to: Considering a release

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > Nearby there's also a `generic_modbus" name. Wondering if the new driver > should be (similar to) `generic_gpio`. sound good. It would be nice if there were an abstraction layer for various GPIO access methods, rather than hard-coding linux, even if there is only one implementation of the

Did refactoring to better split library specifics, now see open/close/read lines that any library should support. Need to split into 2 files, may to go for library? On 2/22/23 20:17, Greg Troxel wrote: > Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > >> Nearby there's also a `generic_modbus" name. Wondering if the new driver >>

Hello all, It was brought to my attention that : Something is not right about the digesting system for nut-upsuser. For example, I received 9 digests dated 15 May 2025. The first of these had 3 messages and all the others only one each. I would like to get one digest per day with all of the messages for that day. Maybe the threshold for sending out the digest because it is "too

Hello all, It was brought to my attention that : Something is not right about the digesting system for nut-upsuser. For example, I received 9 digests dated 15 May 2025. The first of these had 3 messages and all the others only one each. I would like to get one digest per day with all of the messages for that day. Maybe the threshold for sending out the digest because it is "too

hi, I''ve successfully implemented shaping and policing with HTB for my SDSL line. Some tips&tricks I discovered which were not covered in the FAQs and docs I read: - To discover the appropriate rate for your line, flood it with traffic and reduce the rate until the matching class starts to show a consistent backlog -- only then you''ve managed to take the queue away

Cheers all, you may have seen related preparatory news on the NUT website or in the README changes, but now the next step is official: The fine folks at DigitalOcean approved FOSS sponsoring credits to re-host the custom-built multi-platform non-regression NUT CI farm, which builds several hundred scenarios per iteration (to cover a matrix with many OSes, toolkit versions and

Cheers all, you may have seen related preparatory news on the NUT website or in the README changes, but now the next step is official: The fine folks at DigitalOcean approved FOSS sponsoring credits to re-host the custom-built multi-platform non-regression NUT CI farm, which builds several hundred scenarios per iteration (to cover a matrix with many OSes, toolkit versions and

FWIW, there is precedent with libusb{1,0}, libshut and libhid which abstract NUT operations from a "backend lib" to build against; similar for serial.c used by many drivers. Take care to not conflict by filenames with "real" third-party libs used by the build - especially to avoid mixups for headers and in docs/discussion. Jim On Thu, Feb 23, 2023, 22:16 MODRIS B?RZONIS

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > Are there many digest subscribers currently active? WDYT about raising the > size threshold significantly (500K? more?) or abolishing it and just going > for one digest per day? > > I guess the setting is there to make heated discussions (much traffic) > visible faster. I suppose it does not impact

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > Are there many digest subscribers currently active? WDYT about raising the > size threshold significantly (500K? more?) or abolishing it and just going > for one digest per day? > > I guess the setting is there to make heated discussions (much traffic) > visible faster. I suppose it does not impact

Hello all, During holiday revision of issues (hoping to tie up loose ends and get to NUT v2.8.1 soonish), an old https://github.com/networkupstools/nut/issues/50 ticket came to my attention - that some years ago "we" (as NUT community) wanted to create an unified driver for devices with a Modbus connection -- similar to `nutdrv_qx` doing everything about Megatec Qx protocol family

Hello all, During holiday revision of issues (hoping to tie up loose ends and get to NUT v2.8.1 soonish), an old https://github.com/networkupstools/nut/issues/50 ticket came to my attention - that some years ago "we" (as NUT community) wanted to create an unified driver for devices with a Modbus connection -- similar to `nutdrv_qx` doing everything about Megatec Qx protocol family

Great, thanks! Also just for context, this sounded reminiscent of one of the first NUT drivers, `genericups` (for simple contact-closure support, with IIRC serial-port connections rather than GPIO). Nearby there's also a `generic_modbus" name. Wondering if the new driver should be (similar to) `generic_gpio`. @Community verdict: Then there was also an effort some years ago to name

In short try calling speex_encode_int and speex_decode_int. The calls to speex_encode and speex_decode expects the data to be a floating point values. The data is passed by pointer and the compiler does not do the conversion. This is why you are getting the segfault on decode as the short is 16-bits and a standard float is 32-bits. Tom -----Original Message----- From:

Hi Tom, Thanks for your reply, I'm having a few difficulty's following you advise. You mention that I should be calling 'speex_encoder_int' & 'speex_decoder_int', I'm having problems finding these functions in the speex header. I am currenlty calling speex_encoder_init & speex_decoder_init in my test code, I have repeated the relevent bits of the example

On Nov 15, 2013, at 11:16 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > Taking a really quick at the gold code it looks like it tries to keep > 8176 files open. I would suggest putting a breakpoint in > Descriptors::close_some_descriptor and checking why it is failing to > close the files. That is a lot of file descriptors to keep open. It's well above my

CareerEncore (www.careerencore.com) has been exclusively engaged to help our client, a Boston VC backed start-up, to conduct a search for a Director of Technology. This is a unique opportunity for a RoR Developer to step into a hands-on leadership role. The envisioned hire is currently a Senior Engineer who is looking to make the jump into a hands-on leadership role. Our client is only

Hello, All! I found that Samba checks description fields encoding at various tdb files to late. Case 1. FreeBSD with UTF-8 support. At some cases FreeBSD's adduser script can save incorrect UTF-8 sequence to GECOS /etc/passwd field. (Here is example http://www.acc.tula.ru/~acc107_3/samba/miscoding/gecos.txt) When user is added to Samba, Samba reads GECOS field "as is" without

Just a guess, but it might have something to do with the chrome build using thin archives. On 15 November 2013 11:30, Stephen Checkoway <s at pahtak.org> wrote: > > On Nov 15, 2013, at 11:16 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >> Taking a really quick at the gold code it looks like it tries to keep >> 8176 files open. I would suggest

Hello, i need run cibercontrol 4.0 for lucio perri, but it's use mdac, when execute wine cibercontrol, it's show a error of ole ERROR OLE 888ffff, and i install the nativ's libs, quartz.dll mx3ml.dll, and this is fix but the error is "ERROR OLE 800004000" and i don't know how to fix that!! anybody haves problems with MDAC Libs?? or something like this?? Bye and thanks!!