Bug 6047
Summary: | New version of ps breaks existing scripts | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | tchrist |
Component: | procps | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | procps-bugs, tchrist |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-06-19 14:54:31 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
tchrist
1999-10-18 12:30:18 UTC
I have verified that this does work properly in 5.2 but no longer in 6.0 and 6.1. I am assigning this report to the proper developer. ps is in the "procps" component. This is an historical accident, back from when we had ps (kmem-based) and procps had to be distinguished from the kmem-based ps. Added procps-bugs to CC list so that I can review this when looking at procps bugs in my normal manner. :-) This will be fixed in procps-2.0.7. I do not yet have a release date set. 'still recognize it' is flat-out wrong Works for me in 2.0.7-14 at least. |