SIGHUP is now relayed to the command. Bug #719
This commit is contained in:
@@ -375,9 +375,9 @@ CCOOMMMMAANNDD EEXXEECCUUTTIIOONN
|
||||
SSiiggnnaall hhaannddlliinngg
|
||||
When the command is run as a child of the ssuuddoo process, ssuuddoo will relay
|
||||
signals it receives to the command. Unless the command is being run in a
|
||||
new pty, the SIGHUP, 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
|
||||
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
|
||||
instead of SIGSTOP when you wish to suspend a command being run by ssuuddoo.
|
||||
@@ -608,4 +608,4 @@ DDIISSCCLLAAIIMMEERR
|
||||
file distributed with ssuuddoo or http://www.sudo.ws/license.html for
|
||||
complete details.
|
||||
|
||||
Sudo 1.8.15 August 9, 2015 Sudo 1.8.15
|
||||
Sudo 1.8.15 September 15, 2015 Sudo 1.8.15
|
||||
|
Reference in New Issue
Block a user