Fix docs on --sig-proxy to match current behaviour

Signals are proxied to the container process whether or not
the tty is used

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

Closes: #984
Approved by: mheon
This commit is contained in:
Daniel J Walsh
2018-06-22 05:29:56 -04:00
committed by Atomic Bot
parent 088d5af879
commit 3092d20847

View File

@ -523,7 +523,7 @@ If you omit the unit, the system uses bytes. If you omit the size entirely, the
**--sig-proxy**=*true*|*false*
Proxy received signals to the process (non-TTY mode only). SIGCHLD, SIGSTOP, and SIGKILL are not proxied. The default is *true*.
Proxy signals sent to the `podman run` command to the container process. SIGCHLD, SIGSTOP, and SIGKILL are not proxied. The default is *true*.
**--stop-signal**=*SIGTERM*