search for: 2nded

...issue with breaking backward compat here, so if that suits you all, we can go on implementing that... > > It would also be useful to have the output of dmesg (or at least the > USB-related subset), in case it has additional information on why > libusb_get_interrupt() is failing. > 2nded, along with your comment that I don't see any difference between drivers startup process at boot time or later on, WRT to the mentioned context. the only point I also see would be some noise (interferences) tied to other processes looking at USB devices. Beside from Charles requested test, I w...

Not to pick on anyone in particular, but for the sake of organization, I think we might need to address the need for variables beyond the standard ones defined here: http://networkupstools.org/docs/developer-guide.chunked/apas01.html From http://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#_variable_names : "PLEASE don?t make up new variables and commands just because

...ecifics. there is no big issue with breaking backward compat here, so if that suits you all, we can go on implementing that... It would also be useful to have the output of dmesg (or at least the USB-related subset), in case it has additional information on why libusb_get_interrupt() is failing. 2nded, along with your comment that I don't see any difference between drivers startup process at boot time or later on, WRT to the mentioned context. the only point I also see would be some noise (interferences) tied to other processes looking at USB devices. Beside from Charles requested test, I wo...

[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

That worked out just fine. What I am currently running into are conditions where I am getting the following error that I figured I would share. Error: libusb_get_interrupt() returned 0 instead of 8 while sending 3a 4d b2 0d 00 00 00 00 '.M......' Conditions: upsdrvctl start via Init Script at Boottime. If I run the init script after boot, I do not receive this error. Eric Cobb ekcobb