Description of problem: system-config-status shows always "/usr/bin/tor is running" Version-Release number of selected component (if applicable): tor-0.1.2.18-4.fc9 How reproducible: always the reason is in /etc/init.d/tor. the status() function calls "pidofproc" which does not exist. Use /sbin/pidof instead then it works.
[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 --- #!/bin/sh . /lib/lsb/init-functions a=$(pidofproc foobar) ps $a --- returns | $ /tmp/foobar | PID TTY STAT TIME COMMAND | 26016 pts/117 S+ 0:00 /bin/sh /tmp/foobar redhat-lsb-3.1-19.fc8
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...
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 initscript.
*** Bug 425998 has been marked as a duplicate of this bug. ***
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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.