Bug 1255183
Summary: | lastcomm missing '--pid' flag that was present in RHEL6 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Frank Hirtz <fhirtz> | ||||
Component: | psacct | Assignee: | Jan Rybar <jrybar> | ||||
Status: | CLOSED ERRATA | QA Contact: | David Jež <djez> | ||||
Severity: | medium | Docs Contact: | Lenka Kimlickova <lkimlick> | ||||
Priority: | unspecified | ||||||
Version: | 7.2 | CC: | bnater, isenfeld, jrybar, kdudka, ovasik | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Fixed In Version: | psacct-6.6.1-12.el7 | Doc Type: | Release Note | ||||
Doc Text: |
"lastcomm" now supports the "--pid" option
The "lastcomm" command now supports the "--pid" option. This option shows the process ID (PID) and parent-process ID (PPID) for each record if supported by the kernel.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-08-01 20:35:48 UTC | Type: | Bug | ||||
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: | 1298243, 1380361, 1393867 | ||||||
Attachments: |
|
Description
Frank Hirtz
2015-08-19 21:08:08 UTC
Hello Frank. The --pid switch was introduced by the previous component maintainer. Unfortunately the patch didn't get upstream for some reason. I could try to forward-port this and propagate upstream. Let's see how that goes. Thanks, Jaromir. Hello Frank. The project has a bug tracker on savannah. https://savannah.gnu.org/bugs/?group=acct You could also try to contact Markus Gothe <nietzsche.se> directly. Created attachment 1249792 [details]
lastcomm shows PID and PPID if supported
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1953 |