85892 – baselayout: Can't run "/etc/init.d/* status" as unprivileged user

Bug 85892 - baselayout: Can't run "/etc/init.d/* status" as unprivileged user

Summary: baselayout: Can't run "/etc/init.d/* status" as unprivileged user

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] baselayout (show other bugs)
Hardware:	All All

Importance:	High minor (vote)
Assignee:	Gentoo's Team for Core System packages

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-03-19 05:27 UTC by Stuart Shelton
Modified:	2005-05-14 13:35 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Stuart Shelton 2005-03-19 05:27:36 UTC

Following on from the changes from Bug 48595...

If you run "/etc/init.d/<service> status" and any UID != 0, then it silently fails.

However, shouldn't users at least be able to determine whether a service is running, even if they can't start or stop it?

I think the logic needs to allow anyone to run "status", but still fail for non-root start/stop.

(Backgound: I want to run the GNUstep setup script from .bashrc iff the gnustep service is running)

Comment 1 Sam 2005-03-19 10:14:19 UTC

I can't reproduce the silent failure on my system - the script exits with "You must be root to run init scripts" even when the argument "status" is passed. 
You have a valid point though.

Comment 2 Stuart Shelton 2005-03-19 10:49:27 UTC

Yeah, I thought that was odd too (especially after looking at runscript.sh), but I can confirm that whilst any of the scripts do fail ($? == 1), and I see no output.

Comment 3 SpanKY gentoo-dev

2005-05-14 13:35:24 UTC

fixed in baselayout-1.11.12