Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 223147

Summary: pidofproc the not accept -p argument
Product: Red Hat Enterprise Linux 4 Reporter: Neil Schemenauer <nas-redhat>
Component: redhat-lsbAssignee: Lawrence Lim <llim>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: bugzilla, tools-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 15:57:51 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:

Description Neil Schemenauer 2007-01-17 23:57:55 UTC
Description of problem:

As per title.  Red Hat Enterprise Linux 4 claims to conform to the LSB 3.0.  It
seems quite surprising to me that no one has noticed this bug.  See
http://refspecs.freestandards.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/iniscrptfunc.html
.
====================================================
$ . /lib/lsb/init-functions
$ pidofproc -p /var/run/klogd.pid klogd
pidof: invalid options on command line!

pidof: invalid options on command line!
====================================================

Debian and SuSE get this right I believe.  It looks like 'killproc' has the same
bug.

Comment 1 Ragnar Kjørstad 2009-02-12 19:09:36 UTC
start_daemon also have the same problem.

Comment 2 Jiri Pallich 2012-06-20 15:57:51 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.