Bug 685073

Summary:	during shutdown the ups service cause plymouth printing: request came from non-root user
Product:	[Fedora] Fedora	Reporter:	Sandro Bonazzola <sandro.bonazzola>
Component:	nut	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	14	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-04-04 08:37:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sandro Bonazzola 2011-03-15 08:41:16 UTC

This bug doesn't seems to produce any failure and I don't know if this could lead to other issues, but I think it should be investigated.

Description of problem:
During shutdown with ups service enabled plymouth write:

request came from non-root user

It seems that the ups script is running without root privileges.

Version-Release number of selected component (if applicable):
nut-client-2.6.0-2.fc14.i686

How reproducible:
always reproducible

Steps to Reproduce:
1. install nut-client
2. configure an ups
3. shutdown the system
  
Actual results:
"request came from non-root user" is printed by plymouth

Expected results:
the ups script should be executed as root user as other scripts during shutdown, so plymouth should not write "request came from non-root user"

Comment 1 Michal Hlavinka 2011-03-15 14:36:37 UTC

could you check if there is anything about this in logs?

Comment 2 Sandro Bonazzola 2011-03-15 19:43:48 UTC

Nothing, rsyslog is stopped before ups service.

Comment 3 Michal Hlavinka 2012-04-04 08:37:26 UTC

Fedora 14 changed to end-of-life (EOL) status on 2011-12-09. Fedora 14 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.