Description of problem: Can't start nut ups monitoring after latest update because upsdrvctl was put in /sbin but nut-driver.service refers to /usr/sbin/upsdrvctl. Version-Release number of selected component (if applicable): 2.6.4-1.fc16 How reproducible: Imminently Additional info: Link from /usr/sbin/ to /sbin/upsdrvctl solves problem. I assume that fixing the exec definition in /lib/systemd/system/nut-driver.service would work as well.
Right, this path is generated build script, but it should be @driveexecdir@ instead of @SBINDIR@. This bug is in systemd/system/nut-driver.service and systemd/system-shutdown/nutshutdown I'll fix that.
nut-2.6.4-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/nut-2.6.4-2.fc16
Package nut-2.6.4-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nut-2.6.4-2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-10277/nut-2.6.4-2.fc16 then log in and leave karma (feedback).
*** Bug 838192 has been marked as a duplicate of this bug. ***
*** Bug 839019 has been marked as a duplicate of this bug. ***
nut-2.6.4-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.