lagertonne/nut
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Wiki Activity

Imported Upstream version 2.7.4

Browse source
This commit is contained in:
Laurent Bigonville 2016-07-18 02:11:41 +02:00
parent fd413a3168
commit c9cb2187ee
290 changed files with 7473 additions and 2607 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/FAQ.txt
View file

@ -561,6 +561,8 @@ The most frequent issue is that udev has not actually applied the rule:
- and if the device USB cord was already plugged when installing NUT.
In this case, just unplug and plug back the USB cord, then restart NUT.
Instead of unplugging, you might also be able to run `udevadm trigger
--subsystem-match=usb --action=change` to fix permissions.
There was a mistake in the naming of the NUT udev rules file which resulted in
the rules being overridden by another udev configuration file. While this has
@ -590,7 +592,7 @@ will appear in dmesg:
usbfs: process 29641 (usbhid-ups) did not claim interface 0 before use
This can be a symptom of a source install conflicting with a package install.
There is a rudimetary locking mechanism in NUT, but there is a chance that the
There is a rudimentary locking mechanism in NUT, but there is a chance that the
packages might not use the same directory as the NUT default, and the conflict
will be reported by the kernel.