Bug 848491

Summary:	systemctl enable nut-driver.service fails to work
Product:	[Fedora] Fedora	Reporter:	Trever Adams <trever>
Component:	nut	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17	CC:	mhlavink
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-16 07:46:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Trever Adams 2012-08-15 18:42:03 UTC

Description of problem:
# systemctl enable nut-driver.service 
The unit files have no [Install] section. They are not meant to be enabled using systemctl.


Version-Release number of selected component (if applicable):
nut-2.6.4-1.fc17.x86_64
nut-client-2.6.4-1.fc17.x86_64


How reproducible:
Everytime


Additional info:
I am still working on learning systemd stuff, I tried adding the Install section and an "WantedBy=" line. Nothing there works.

Comment 1 Michal Hlavinka 2012-08-16 07:46:16 UTC

NOTABUG
You don't want to enable nut-driver by hand, it's started only on demand.
a)you have locally attached ups, then you need nut-server.service (it has Requires=nut-driver.service so it will start nut-driver.service itself) and (in most cases also) nut-client.service

b)ups is attached to different computer and you want to know its status, then you need nut-client.service only

Comment 2 Trever Adams 2012-08-16 18:14:36 UTC

# service nut-client restart
Redirecting to /bin/systemctl restart  nut-client.service
Failed to issue method call: Unit nut-client.service failed to load: No such file or directory. See system logs and 'systemctl status nut-client.service' for details.

I forgot to include this in my initial report. Sorry. Did you mean nut-monitor?

Comment 3 Michal Hlavinka 2012-08-20 10:43:17 UTC

> I forgot to include this in my initial report. Sorry. Did you mean
> nut-monitor?

Yes, it should be nut-monitor.service from nut-client rpm package