We've been trapping SIGQUIT for a "clean shutdown" since commit
3cad436a
However, sources such as:
http://www.gnu.org/software/libc/manual/html_node/Termination-Signals.html
indicate we probably shouldn't be trapping it at all, as the intent of
SIGQUIT is to leave a core file and debug artifacts from the run.
We should perform the minimal amount of clean up to ensure the system isn't
left in an unusable state - but these days that's performed by other
software such as logind.
We can safely stop trapping SIGQUIT entirely.
(Based on work from https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/817)
Bug-AGL: SPEC-4570
Signed-off-by: Derek Foreman <derek.foreman@collabora.com>
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: Icf7d4f3e76a58e781bad911a966b65e2798266d0
char *cmdline;
struct wl_display *display = NULL;
struct wl_event_loop *loop;
- struct wl_event_source *signals[3] = { 0 };
+ struct wl_event_source *signals[2] = { 0 };
struct weston_config_section *section;
/* Command line options */
char *backend = NULL;
display);
signals[1] = wl_event_loop_add_signal(loop, SIGINT, on_term_signal,
display);
- signals[2] = wl_event_loop_add_signal(loop, SIGQUIT, on_term_signal,
- display);
for (size_t i = 0; i < ARRAY_LENGTH(signals); ++i)
if (!signals[i])