Relaunch on SIGUSR2
feat: relaunch on SIGUSR2 (#4979)
Relaunch on SIGUSR2featrelaunch sigusr2
Committed by code-asher
commit message
feat: relaunch on SIGUSR2 (#4979)
This is because Node uses SIGUSR1 to enable the debug listener so even
if you just want to restart code-server you end up enabling the debug
listener as well.
Opted to leave the SIGUSR1 handler in to avoid breaking existing
workflows even though it does mean even if you only want to enable the
debug listener you will end up restarting code-server as well. We could
consider removing it after a transition phase.Editor assessment
`feat: relaunch on SIGUSR2 (#4979)` states the signal chosen, and the body is a model of trade-off explanation: SIGUSR1 was unusable because Node binds it to the debug listener, the old handler is deliberately kept to avoid breaking existing workflows, the accepted cost is stated, and a transition plan is proposed. Motivation, alternatives considered, and future direction — the full set of things a body can teach — in compact prose. Feat is accurate, the subject is imperative and period-free, and nothing is malformed. An exemplar.