From 57231d4acf41ac01aa96a558c8d3017054b15269 Mon Sep 17 00:00:00 2001 From: Ophestra Date: Thu, 23 Oct 2025 08:02:03 +0900 Subject: container/init: improve signal handling The SIGTERM signal is delivered in many other cases and can lead to strange behaviour. The unconditional resume of the logger also causes strange behaviour in the cancellation forwarding path. This change also passes through additional signals. Signed-off-by: Ophestra --- container/container.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'container/container.go') diff --git a/container/container.go b/container/container.go index fb031c38..55e4c441 100644 --- a/container/container.go +++ b/container/container.go @@ -24,7 +24,7 @@ import ( const ( // CancelSignal is the signal expected by container init on context cancel. // A custom [Container.Cancel] function must eventually deliver this signal. - CancelSignal = SIGTERM + CancelSignal = SIGUSR2 ) type ( -- cgit v1.3.1