Clarify when SIGINT and SIGQUIT are relayed by sudo to the command.

diff --git a/doc/sudo.cat b/doc/sudo.cat
index 95544a7d39bb945baa8801662f7f3368a7e8f09d..90b061b8db7cea9b57bde597237ed5f3464d8072 100644 (file)
--- a/doc/sudo.cat
+++ b/doc/sudo.cat
@@ -374,12 +374,12 @@ C\bCO\bOM\bMM\bMA\bAN\bND\bD E\bEX\bXE\bEC\bCU\bUT\bTI\bIO\bON\bN
 
    S\bSi\big\bgn\bna\bal\bl h\bha\ban\bnd\bdl\bli\bin\bng\bg
      When the command is run as a child of the s\bsu\bud\bdo\bo process, s\bsu\bud\bdo\bo will relay
-     signals it receives to the command.  Unless the command is being run in a
-     new pty, the SIGINT and SIGQUIT signals are not relayed unless they are
-     sent by a user process, not the kernel.  Otherwise, the command would
-     receive SIGINT twice every time the user entered control-C.  Some
-     signals, such as SIGSTOP and SIGKILL, cannot be caught and thus will not
-     be relayed to the command.  As a general rule, SIGTSTP should be used
+     signals it receives to the command.  The SIGINT and SIGQUIT signals are
+     only relayed when the command is being run in a new pty or when the
+     signal was sent by a user process, not the kernel.  This prevents the
+     command from receiving SIGINT twice each time the user enters control-C.
+     Some signals, such as SIGSTOP and SIGKILL, cannot be caught and thus will
+     not be relayed to the command.  As a general rule, SIGTSTP should be used
      instead of SIGSTOP when you wish to suspend a command being run by s\bsu\bud\bdo\bo.
 
      As a special case, s\bsu\bud\bdo\bo will not relay signals that were sent by the

diff --git a/doc/sudo.man.in b/doc/sudo.man.in
index d55dcc62fdc8af9a44aefd6748dc32f071953315..6350b0566b36ba393d54834d18995dcb965b047c 100644 (file)
--- a/doc/sudo.man.in
+++ b/doc/sudo.man.in
@@ -730,15 +730,15 @@ When the command is run as a child of the
 process,
 \fBsudo\fR
 will relay signals it receives to the command.
-Unless the command is being run in a new pty, the
+The
 \fRSIGINT\fR
 and
 \fRSIGQUIT\fR
-signals are not relayed unless they are sent by a user process,
-not the kernel.
-Otherwise, the command would receive
+signals are only relayed when the command is being run in a new pty
+or when the signal was sent by a user process, not the kernel.
+This prevents the command from receiving
 \fRSIGINT\fR
-twice every time the user entered control-C.
+twice each time the user enters control-C.
 Some signals, such as
 \fRSIGSTOP\fR
 and

diff --git a/doc/sudo.mdoc.in b/doc/sudo.mdoc.in
index 44674875a7c340fce0508a15e4ad505ed614c6e8..f2cb8d9fe71e00ec88102ae72b626861be89c599 100644 (file)
--- a/doc/sudo.mdoc.in
+++ b/doc/sudo.mdoc.in
@@ -665,15 +665,15 @@ When the command is run as a child of the
 process,
 .Nm
 will relay signals it receives to the command.
-Unless the command is being run in a new pty, the
+The
 .Dv SIGINT
 and
 .Dv SIGQUIT
-signals are not relayed unless they are sent by a user process,
-not the kernel.
-Otherwise, the command would receive
+signals are only relayed when the command is being run in a new pty
+or when the signal was sent by a user process, not the kernel.
+This prevents the command from receiving
 .Dv SIGINT
-twice every time the user entered control-C.
+twice each time the user enters control-C.
 Some signals, such as
 .Dv SIGSTOP
 and