Bug 2150486

Summary:	usbhid-ups attempts to write to /var/run instead of /run
Product:	[Fedora] Fedora	Reporter:	David While <dwhile>
Component:	nut	Assignee:	Charles R. Anderson <cra>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	37	CC:	cra, james, mhlavink, orion, scott
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-03 17:35:58 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 David While 2022-12-03 10:57:53 UTC

Description of problem:

When starting the nut-server using the usbhid-ups driver, the service fails to start due to usbhid-ups driver attempting to write the pid file to /var/run which it doesn't have permission for. It should write to /run


Version-Release number of selected component (if applicable):


How reproducible:

Very


Steps to Reproduce:
1. Configure nut-server to use usbhid-ups driver to access a UPS
2. Start the service
3.

Actual results:

Service doesn't start

Expected results:

Service should start normally


Additional info:

Comment 1 Charles R. Anderson 2022-12-03 17:35:58 UTC


*** This bug has been marked as a duplicate of bug 2143442 ***