Cory Snider d9bdb61992 cmd/dockerd: use default SIGQUIT behaviour ... dockerd handles SIGQUIT by dumping all goroutine stacks to standard error and exiting. In contrast, the Go runtime's default SIGQUIT behaviour... dumps all goroutine stacks to standard error and exits. The default SIGQUIT behaviour is implemented directly in the runtime's signal handler, and so is both more robust to bugs in the Go runtime and does not perturb the state of the process to anywhere near same degree as dumping goroutine stacks from a user goroutine. The only notable difference from a user's perspective is that the process exits with status 2 instead of 128+SIGQUIT. Signed-off-by: Cory Snider <csnider@mirantis.com> (cherry picked from commit 0867d3173c) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>		2023-01-17 13:41:01 +01:00
..
docker-proxy	cmd/docker-proxy: add "-v / --version" flag	2022-12-28 08:24:47 +01:00
dockerd	cmd/dockerd: use default SIGQUIT behaviour	2023-01-17 13:41:01 +01:00