Bug 162068

Summary: pidof: -x does not work as expected
Product: Red Hat Enterprise Linux 3 Reporter: Bastien Nocera <bnocera>
Component: SysVinitAssignee: Bill Nottingham <notting>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: rvokal, tao
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2005-510 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-28 20:00:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 156320    

Description Bastien Nocera 2005-06-29 16:49:50 UTC
The same still occurs on RHEL3 (but was fixed on RHEL4).

+++ This bug was initially created as a clone of Bug #85796 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
if i have the following process given by ps -efw
root      8484     1  0 15:34 pts/1    00:00:00 /usr/bin/python
/usr/local/bin/nodeinfo

in 8.0 i dont get the expected process id if i do pidof -x /usr/local/bin/nodeinfo: 

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


How reproducible:
Always

Steps to Reproduce:
1.create a small script eg /usr/local/bin/nodeinfo in python 
2. run it with python /usr/local/bin/nodeinfo
3.Try to find process id using 
    pidof -x /usr/local/bin/nodeinfo

Actual Results:  in redhat 8.0
[root]# pidof -x /usr/local/bin/nodeinfo

[root]# 


Expected Results:  in redhat 7.3
[root]# pidof -x /usr/local/bin/nodeinfo
8484
root]# 


Additional info:

--

Comment 6 Red Hat Bugzilla 2005-09-28 20:00:58 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-510.html