Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[lipstick] Do not change signal handlers on shutdown. JB#60078 #38

Merged
merged 2 commits into from Feb 7, 2023

Conversation

spiiroin
Copy link
Contributor

@spiiroin spiiroin commented Feb 6, 2023

Getting a shutdown notification basically means that we are going to get a TERM signal in a couple of seconds. Using that as a cue for substituting TERM handler that triggers lipstick to make a clean exit with something else makes little sense. Especially as the candidates are async-signal unsafe code from hwcomposer-plugin (that can hang and require KILL) or default handler that makes quick and dirty exit (potentially leaving behind e.g. lock files).

Keep using the already installed lipstick signal handlers.

Signed-off-by: Simo Piiroinen simo.piiroinen@jolla.com

Getting a shutdown notification basically means that we are going to
get a TERM signal in a couple of seconds. Using that as a cue for
substituting TERM handler that triggers lipstick to make a clean
exit with something else makes little sense. Especially as the
candidates are async-signal unsafe code from hwcomposer-plugin (that
can hang and require KILL) or default handler that makes quick and
dirty exit (potentially leaving behind e.g. lock files).

Keep using the already installed lipstick signal handlers.

Signed-off-by: Simo Piiroinen <simo.piiroinen@jolla.com>
Remove dead code, data and references in unit tests too.

Signed-off-by: Simo Piiroinen <simo.piiroinen@jolla.com>
@spiiroin spiiroin merged commit 31a076f into sailfishos:master Feb 7, 2023
@spiiroin spiiroin deleted the jb60078_keep_signal_handlers branch February 7, 2023 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants