search for: lcnc

...n/nut total 8 -rw-r--r-- 1 nut nut 6 May 7 10:40 upsd.pid -rw-r--r-- 1 root root 6 May 7 10:43 upsmon.pid The real problem as I recall from a couple days back, is that the usbhid-ups driver was left out of this kernel build. Since this is pretty close to an rt kernel, I don't know if the LCNC folks will build another kernel with it, and issue the update. I have made them aware of it however. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <ht...

On May 8, 2019, at 8:19 PM, Gene Heskett wrote: > > The real problem as I recall from a couple days back, is that the > usbhid-ups driver was left out of this kernel build. Since this is > pretty close to an rt kernel, I don't know if the LCNC folks will build > another kernel with it, and issue the update. Since you mentioned this in the other thread, I just want to clarify again that "usbhid-ups" is *not* a kernel driver. There is a possibility that the LCNC folks have changed their kernel configuration, but they won'...

    I just set up a UPS on a Debian Stretch system for my sister-in-law.  Obviously, I want NUT to properly shut down the unit when the battery gets low.  This means upsmon must be running and healthy.  When I run 'systemctl status nut-monitor`, I see the following in the journal: nut-monitor.service: Supervising process 778 which is not our child. We'll most likely not notice when

On Tuesday 07 May 2019 09:49:47 am Charles Lepple wrote: > On May 7, 2019, at 9:09 AM, Gene Heskett wrote: > > On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > >> On May 7, 2019, at 5:06 AM, Gene Heskett wrote: > >>> New testing install(stretch) > >>> pulled in nut stuff from repo. > >>> copied old wheezy configs to /etc/nut,