summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDebarshi Ray <rishi@fedoraproject.org>2019-01-08 14:32:52 +0100
committerDebarshi Ray <rishi@fedoraproject.org>2019-01-08 16:34:09 +0100
commite02199f2a401079375454acb639534c6f4f83c7f (patch)
tree03b511bfb3b2b5871105f778ae570eb8e1e4a0f9 /docs
parentf71264e6126fa889306693b97177128da05836fe (diff)
downloadpodman-e02199f2a401079375454acb639534c6f4f83c7f.tar.gz
podman-e02199f2a401079375454acb639534c6f4f83c7f.tar.bz2
podman-e02199f2a401079375454acb639534c6f4f83c7f.zip
Default --sig-proxy to true for 'podman start --attach'
The --sig-proxy option in both 'podman attach' and 'podman run' default to true, and there's no reason for 'podman start --attach' to be any different. However, since it only makes sense to proxy signals when the container is attached, 'podman start --sig-proxy' will continue to error if --attach isn't used. Signed-off-by: Debarshi Ray <rishi@fedoraproject.org>
Diffstat (limited to 'docs')
-rw-r--r--docs/podman-start.1.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/podman-start.1.md b/docs/podman-start.1.md
index cfd44ac3a..f16a20efa 100644
--- a/docs/podman-start.1.md
+++ b/docs/podman-start.1.md
@@ -35,7 +35,7 @@ to run containers such as CRI-O, the last started container could be from either
**--sig-proxy**=*true*|*false*
-Proxy received signals to the process (non-TTY mode only). SIGCHLD, SIGSTOP, and SIGKILL are not proxied. The default is false.
+Proxy received signals to the process (non-TTY mode only). SIGCHLD, SIGSTOP, and SIGKILL are not proxied. The default is *true* when attaching, *false* otherwise.
## EXAMPLE