Bug 432254 - 'pidofproc' returns pid of initscripts
Summary: 'pidofproc' returns pid of initscripts
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-lsb   
(Show other bugs)
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Lawrence Lim
QA Contact: Fedora Extras Quality Assurance
: 425998 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2008-02-10 13:51 UTC by Jochen Schlick
Modified: 2014-03-26 00:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 15:57:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jochen Schlick 2008-02-10 13:51:37 UTC
Description of problem:
system-config-status shows always "/usr/bin/tor is running"

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

How reproducible:

the reason is in /etc/init.d/tor. the status() function calls "pidofproc" which
does not exist. Use /sbin/pidof instead then it works.

Comment 1 Enrico Scholz 2008-02-10 14:34:30 UTC
[reassigning to redhat-lsb]

The 'pidofproc' function returns the pid of the initscript and causes bogus
results for the 'status' call. E.g. having a script '/tmp/foobar' like

. /lib/lsb/init-functions
a=$(pidofproc foobar)
ps $a


| $ /tmp/foobar
| 26016 pts/117  S+     0:00 /bin/sh /tmp/foobar


Comment 2 Jochen Schlick 2008-02-10 15:45:45 UTC
hmmm, strange. I have nearly 2 identical systems with rawhide and
redhat-lsb-3.1-19.fc8 and both show the same behaviour as I wrote in my bug report.

here my results when tor is not running:
/etc/init.d:root:# sh tor status
/usr/bin/tor is not running
/etc/init.d:root:# service tor status
/usr/bin/tor is running
/etc/init.d:root:# ./tor status
/usr/bin/tor is running

????? why does /sbin/service, /etc/init.d/tor status report wrong things ?
at the moment I have no idea...

Comment 3 Enrico Scholz 2008-02-10 16:13:11 UTC
when you execute 'sh ...tor', the process name is 'sh'. In the other cases the
script is executed directly and the process name is 'tor'.

'pidofproc' fails in filtering out the pid of the initscript because it spawns
an own process and %PPID in the following 'pidof' call does not point the

Comment 4 Enrico Scholz 2008-02-12 20:06:13 UTC
*** Bug 425998 has been marked as a duplicate of this bug. ***

Comment 5 Bug Zapper 2008-05-14 05:07:22 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 6 Bug Zapper 2009-06-09 23:32:08 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 7 Bug Zapper 2009-07-14 15:57:33 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

Thank you for reporting this bug and we are sorry it could not be fixed.

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