Bug 1518986
Summary: | Please add AUID to list of selectable fields in ps. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Thomas Gardner <thgardne> | ||||
Component: | procps-ng | Assignee: | Jan Rybar <jrybar> | ||||
Status: | CLOSED ERRATA | QA Contact: | Branislav NĂ¡ter <bnater> | ||||
Severity: | medium | Docs Contact: | Marie Hornickova <mdolezel> | ||||
Priority: | medium | ||||||
Version: | 7.6 | CC: | bnater, brett_lowry, fkrska, jrybar, mkyral, vslavik | ||||
Target Milestone: | rc | Keywords: | Improvement, Patch, Upstream | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | procps-ng-3.3.10-21.el7 | Doc Type: | Enhancement | ||||
Doc Text: |
The *ps* utility now displays the Login ID associated with processes
The new format option "luid" of the *ps* utility now enables you to display the Login ID associated with processes.
To display the login ID attributes of running processes, use the following command:
$ ps -o luid
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-10-30 07:56:26 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: | 1477664, 1546815, 1549617, 1549689, 1551061 | ||||||
Attachments: |
|
Description
Thomas Gardner
2017-11-29 22:22:40 UTC
Hello, it seems to be present in upstream as LUID (loginID) ($ ps -o LUID). If that is what you meant, I shall backport it in rhel-7.6. Thanks. Yup. loginID and AUID are synonymous. If we wanna call it LUID, too, welp, I guess we can add another synonym. :-) Oh, yeah, and I'm guessing that the man page will also be updated as part this request reflecting the change in function, right? Of course :) Unless you want to make it an easter egg :D I've just peeked at the history of the LUID feature in upstream and it seems to be present there since 2003. And yes, it's in RHEL7 and Fedora also! It just appears to be missing from manpage. Try the following: $ ps -eo pid,luid,cmd Is it the result expected by the customer? Thanks. PS: manpage fix is on the way. Displaying the the auid is not just a man page fix for the ps command. iaasn00052525# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.8 (Santiago) iaasn00052525# id -a uid=0(root) gid=0(root) groups=0(root) iaasn00052525# date Mon Feb 5 13:31:55 EST 2018 iaasn00052525# ps -eo pid,luid,cmd | head PID LUID CMD 1 - /sbin/init 2 - [kthreadd] 3 - [migration/0] 4 - [ksoftirqd/0] 5 - [stopper/0] 6 - [watchdog/0] 7 - [migration/1] 8 - [stopper/1] 9 - [ksoftirqd/1] iaasn00052525# The LUID is blank in the ps output. This needs to be fixed. Having it work with -o auid would make sense too, as a suggestion. Please move forward with a real fix/update. - Brett Lowry J.P. Morgan Chase. Here is a RHEL 7.3 as well: ashamvarchlab02# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.3 (Maipo) ashamvarchlab02# id -a uid=0(root) gid=0(root) groups=0(root) context=system_u:system_r:unconfined_service_t:s0 ashamvarchlab02# date Mon Feb 5 13:51:17 EST 2018 ashamvarchlab02# ps -eo pid,luid,cmd | head PID LUID CMD 1 - /usr/lib/systemd/systemd --switched-root --system --deserialize 20 2 - [kthreadd] 3 - [ksoftirqd/0] 5 - [kworker/0:0H] 7 - [migration/0] 8 - [rcu_bh] 9 - [rcu_sched] 10 - [watchdog/0] 11 - [watchdog/1] ashamvarchlab02# - Brett Lowry J.P. Morgan Chase. Yes, the code in upstream seems like a preparation for the functionality, but without an actual implementation. The patch implementing the functionality has been sent to upstream. It will be merged into the nearest RHEL minor release as quickly as it gets merged into upstream. Comments welcomed. Created attachment 1393936 [details]
proposed patch
Fix accepted by upstream. This BZ proposed to rhel-7.6. 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-2018:3045 |