diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2014-07-21 07:54:29 +0100 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2014-07-21 16:32:42 +0100 |
| commit | 4f7d4dcae56e5f993f3f0b331556d4df3b0b33ab (patch) | |
| tree | 8723973cbb93a94ef5cf457f50ea7efb95c10a9c /lib/igt_core.h | |
| parent | 4d4f4b213ca95dad59bdf8080d7bb034aa2d307a (diff) | |
Use SIGTERM in replace of SIGQUIT
SIGTERM is the normal signal to use when instructing a process to exit.
The only difference is that an unhandled SIGQUIT is meant to generate a
coredump, which is not what we want, but in practice I encountered an
issue where SIGTERM seemed to be deliverable more reliably than SIGQUIT
(in tests using multiple signal helpers).
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'lib/igt_core.h')
| -rw-r--r-- | lib/igt_core.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/igt_core.h b/lib/igt_core.h index a30d0d14..61384878 100644 --- a/lib/igt_core.h +++ b/lib/igt_core.h @@ -372,7 +372,7 @@ void igt_waitchildren(void); /** * igt_helper_process_t: * @running: indicates whether the process is currently running - * @use_SIGKILL: whether the helper should be terminated with SIGKILL or SIGQUIT + * @use_SIGKILL: whether the helper should be terminated with SIGKILL or SIGTERM * @pid: pid of the helper if @running is true * @id: internal id * |