"Is it possible I need to compile NUT myself instead of using the Ubuntu
package?"
Certainly! For me, it's very rare that I install anything that isn't compiled
from source.
As long as you have compilers and any prerequisite packages in place, it's
close to a trivial process.
- Tim
On
> VID 2341 doesn't show up in the NUT Git source tree.
I was curious about this so just searched for Arduino and then 2341. I
found a few hits, but the interesting one was in nut/drivers
/arduino-hid.c
I don't know enough about the project to know what a "subdriver" (that's
what the comments
> On Oct 29, 2023, at 9:25 PM, Kelly Byrd wrote:
>
> I have seen reports of folks claiming this just worked for them out of the
> box,
Here you're referring to just making things work on Windows or macOS, right? I
don't think it will be quite as simple with NUT, mostly because the NUT drivers
> Here you're referring to just making things work on Windows or macOS,
right? I don't think it will be quite as simple with NUT, mostly because
the NUT drivers are trying to expose all of the variables and commands,
rather than just the simple shutdown bits.
By "work with on Windows on macOS" I
Looking at the output of lsub in my original message:
`bNumInterfaces 1`
Then there's only one Interface Descriptor section.
I can modify the USB code the runs on the Arduino, if needed. I'm looking
for help on what is going wrong and what I could modify to fix it. I have
seen reports of
Vojtěch Hurčík via Nut-upsuser
writes:
> Thanks for the reply, it's only reported once per spawned process and
> what you say makes perfect sense in this light. A configuration toggle
> or environment variable also seems like a good idea, but I'm sure I or
> we can also live with the message
OTOH: I wonder whether, when it says "Claimed interface 2 successfully" it
got the right number of the correct (HID) one of many interfaces you likely
have there?.. :\
Jim
On Mon, Oct 30, 2023, 00:04 Kelly Byrd wrote:
>
>
> Apologies for the long post. I'm trying to include what I hope are
Apologies for the long post. I'm trying to include what I hope are the
relevant bits (output of lsusb -v and usbhid-ups)
Long term goal: I've got a DIY UPS that I would like to get working with my
QNAP NAS (which uses Linux and NUT underneath the hood)
Immediate short-term problem:
I can't get
Thanks for the reply, it's only reported once per spawned process and what you
say makes perfect sense in this light. A configuration toggle or environment
variable also seems like a good idea, but I'm sure I or we can also live with
the message being reported once per process as it currently
Would this help?
https://github.com/networkupstools/nut/pull/2136
Jim
On Sun, Oct 29, 2023 at 5:04 PM Vojtěch Hurčík wrote:
> Thanks for the reply, it's only reported once per spawned process and what
> you say makes perfect sense in this light. A configuration toggle or
> environment
Thanks for your concern.
Technically, it is not about just systemd - other systems where launched
processes that have ways to interact with some OS framework (like SMF,
upstart, Windows services, docker/kubernetes, whatever) *and* such
framework offers ways for services to inform they have
Hello friends!
With the upcoming NUT release there is one thing I would like to ask:
-
no notification tech defined, will not spam more about
I am repeatedly getting these messages in my syslog more recently because I do
not have systemd available to me on my distribution and also do not want
12 matches
Mail list logo
