aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEd Santiago <santiago@redhat.com>2018-03-06 13:50:03 -0700
committerAtomic Bot <atomic-devel@projectatomic.io>2018-03-06 23:32:33 +0000
commite8fbe93e29028aa6c140c5c42bfe58917860ed81 (patch)
tree778101fa8b12de35fd23e6c6fc08b4610ffaf5fc /docs
parentbbf9a313c3f835f452cfab0dd09f13116f673814 (diff)
downloadpodman-e8fbe93e29028aa6c140c5c42bfe58917860ed81.tar.gz
podman-e8fbe93e29028aa6c140c5c42bfe58917860ed81.tar.bz2
podman-e8fbe93e29028aa6c140c5c42bfe58917860ed81.zip
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 <santiago@redhat.com> Closes: #457 Approved by: rhatdan
Diffstat (limited to 'docs')
-rw-r--r--docs/podman-top.1.md8
1 files 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