Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 20697 - services won't start if another process of the same name is running
services won't start if another process of the same name is running
Status: CLOSED DUPLICATE of bug 20696
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
: Security
Depends On:
  Show dependency treegraph
Reported: 2000-11-11 22:52 EST by Eric Smith
Modified: 2014-03-16 22:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-11-11 22:52:29 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Eric Smith 2000-11-11 22:52:26 EST
The deamon() function in /etc/rc.d/init.d/functions will not start a
service if there is an existing process with the same name, becuase
pidofproc() finds it.  For instance, a user of my system runs a custom
httpd process, completely independent of the installed Apache server.  If I
issue the command "/etc/rc.d/init.d/httpd restart", it will fail, without
giving any indication that there was a problem.

This is a possible Denial of Service attack.  An unprivileged user can
interfere with the operation of any system services managed through
initscripts that uses the deamon() function.

Suggested fix:  add an argument to daemon() and pidofproc() for the
expected UID of the process, perhaps defaulting to root.  Or, by default
allow it to match only UIDs under 100.
Comment 1 Eric Smith 2000-11-11 22:53:42 EST

*** This bug has been marked as a duplicate of 20696 ***
Comment 2 Eric Smith 2000-11-11 22:54:25 EST
Sorry, submitted twice by accident

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