Displaying 3 results from an estimated 3 matches for "usnhid".
Did you mean:
usbhid
2019 May 12
2
nut vs ups fail
...l status nut-driver
● nut-driver.service - Network UPS Tools - power device driver controller
Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor
preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-05-10 02:35:09 EDT;
2 days ago
Ok, I'll byte, the only usnhid-ups on the system is on the old wheezy
drive, and its a 32 bit so won't run on a 64 bit install. ??
Thanks Charles
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)
Ge...
2019 May 12
0
nut vs ups fail
...iver.service - Network UPS Tools - power device driver controller
> Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor
> preset: enabled)
> Active: failed (Result: exit-code) since Fri 2019-05-10 02:35:09 EDT;
> 2 days ago
>
> Ok, I'll byte, the only usnhid-ups on the system is on the old wheezy
> drive, and its a 32 bit so won't run on a 64 bit install. ??
Per https://alioth-lists.debian.net/pipermail/nut-upsuser/2019-May/011389.html I thought you reinstalled NUT, and that was fixed?
At this point, "ps auxww | grep usbhid-ups" sh...
2019 May 09
2
nut vs ups fail
On Wednesday 08 May 2019 05:39:22 pm Stuart D. Gathman wrote:
> On Tue, 7 May 2019, Gene Heskett wrote:
> > May 07 10:40:21 coyote upsd[12110]: fopen /var/run/nut/upsd.pid: No
> > such file or directory
>
> Some time ago, Fedora made /var/run a symlink to /run which is a tmpfs
> filesystem. Thus, any subdirectories must be created afresh each
> boot. The packager for