From e8fbe93e29028aa6c140c5c42bfe58917860ed81 Mon Sep 17 00:00:00 2001 From: Ed Santiago Date: Tue, 6 Mar 2018 13:50:03 -0700 Subject: docs: podman-top: fix nonworking example (minor) One example in the podman-top man page results in an error when actually invoked: unable to find PID field in ps output. try a different set of ps arguments Cause: commit 6cb1c31d (PR #400) has to check PIDs in order to filter those in the container. Solution: add 'pid' to the list of requested output fields in the sample command. Signed-off-by: Ed Santiago Closes: #457 Approved by: rhatdan --- docs/podman-top.1.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/podman-top.1.md b/docs/podman-top.1.md index 1fca50bda..361e2e608 100644 --- a/docs/podman-top.1.md +++ b/docs/podman-top.1.md @@ -33,10 +33,10 @@ to run containers such as CRI-O, the last started container could be from either ``` ``` -#podman --log-level=debug top f5a62a71b07 -o fuser,f,comm,label -FUSER F COMMAND LABEL -root 4 bash system_u:system_r:container_t:s0:c429,c1016 -root 0 vi system_u:system_r:container_t:s0:c429,c1016 +#podman --log-level=debug top f5a62a71b07 -o pid,fuser,f,comm,label + PID FUSER F COMMAND LABEL +18715 root 4 bash system_u:system_r:container_t:s0:c429,c1016 +18741 root 0 vi system_u:system_r:container_t:s0:c429,c1016 # ``` ## SEE ALSO -- cgit v1.2.3-54-g00ecf