Bug 376041 - Cannot check setroubleshoot service status as non-root
Cannot check setroubleshoot service status as non-root
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: setroubleshoot (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: John Dennis
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-11 10:28 EST by Ville Skyttä
Modified: 2008-02-28 16:43 EST (History)
0 users

See Also:
Fixed In Version: setroubleshoot-2.0.2-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-09 12:42:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ville Skyttä 2007-11-11 10:28:51 EST
$ /etc/init.d/setroubleshoot status
(nothing)

This is caused by a too early "test `id -u` = 0  || exit 4" in the init script.
 At least the status action should be allowed for non-root users, and for
actions that require root access, an error message should be emitted instead of
failing silently when run as non-root.
Comment 1 John Dennis 2007-11-12 10:53:22 EST
Good point, will fix...
Comment 2 John Dennis 2008-01-09 12:42:37 EST
fixed in setroubleshoot-2.0.2-1
Comment 3 Fedora Update System 2008-01-15 17:54:56 EST
setroubleshoot-2.0.2-1.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update setroubleshoot'
Comment 4 Fedora Update System 2008-02-25 21:18:51 EST
setroubleshoot-plugins-2.0.4-3.fc8,setroubleshoot-2.0.5-2.fc8 has been submitted as an update for Fedora 8
Comment 5 Fedora Update System 2008-02-28 16:43:02 EST
setroubleshoot-plugins-2.0.4-3.fc8, setroubleshoot-2.0.5-2.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.