Mailinglist Archive: opensuse-bugs (3354 mails)

< Previous Next >
[Bug 962218] nut (Network UPS Tools) systemd .service file has incorrect path
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 27 May 2016 20:32:22 +0000
  • Message-id: <bug-962218-21960-wTS2cBrkFN@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=962218
http://bugzilla.opensuse.org/show_bug.cgi?id=962218#c2

Bill Wayson <bill_wayson@xxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |bill_wayson@xxxxxxxxx

--- Comment #2 from Bill Wayson <bill_wayson@xxxxxxxxx> ---
I can confirm Henryk's experience and diagnosis in his description, and
Tomáš's
comment 1 for Tumbleweed (nut-2.7.3-2.2.x86_64). Tumbleweed's
nut-driver.service file has the correct path for where it deposits the
upsdrvctl file. To fix Leap 42.1 (nut-2.7.1-1.4.x86_64) for a UPS attached to
your PC, become root, save a copy of
/usr/lib/systemd/system/nut-driver.service, edit
/usr/lib/systemd/system/nut-driver.service as described by Henryk and save it,
then run "systemctl daemon-reload". Now "systemctl daemon-reload" and
"systemctl start nut-monitor.service" should run, which can be verified with
the "upsc myups@localhost" command (assuming the rest of the configuration is
correct). If the upsc command does not display a long list of UPS variables,
the problem probably lies elsewhere in the nut configuration.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages