diff options
author | Julian Andres Klode <jak@debian.org> | 2016-08-19 13:00:33 +0200 |
---|---|---|
committer | Julian Andres Klode <jak@debian.org> | 2016-08-19 16:45:03 +0200 |
commit | a6ae3d3df490e7a5a1c8324ba9dc2e63972b1529 (patch) | |
tree | 992d323202c695382eb098fdf6551a461109f4a3 /cmdline/apt-dump-solver.cc | |
parent | 0eaa491c63d0583812a795f872be71ea54e7f01d (diff) |
Ignore SIGINT and SIGQUIT for Pre-Install hooks
Instead of erroring out when receiving a SIGINT, let the
child deal with it - we'll error out anyway if the child
exits with an error or due to the signal. Also ignore
SIGQUIT, as system() ignores it.
This basically fixes Bug #832593, but: we are running
the hooks via sh -c. Some shells exit with a signal
error even if the command they are executing catches
the signal and exits successfully. So far, this has
been noticed on dash, which unfortunately, is our
default shell.
Example:
$ cat trap.sh
trap 'echo int' INT; sleep 10; exit 0
$ if dash -c ./trap.sh; then echo OK: $?; else echo FAIL: $?; fi
^Cint
FAIL: 130
$ if mksh -c ./trap.sh; then echo OK: $?; else echo FAIL: $?; fi
^Cint
OK: 0
$ if bash -c ./trap.sh; then echo OK: $?; else echo FAIL: $?; fi
^Cint
OK: 0
Diffstat (limited to 'cmdline/apt-dump-solver.cc')
0 files changed, 0 insertions, 0 deletions