diff options
| author | Ophestra <cat@gensokyo.uk> | 2025-10-23 08:02:03 +0900 |
|---|---|---|
| committer | Ophestra <cat@gensokyo.uk> | 2025-10-23 08:02:03 +0900 |
| commit | 57231d4acf41ac01aa96a558c8d3017054b15269 (patch) | |
| tree | 433e514e4bca7dd901d001260ef46bf90089f5e6 /container/container.go | |
| parent | c5aefe5e9d28a8d4dad68bc06b38e42101656fe9 (diff) | |
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 <cat@gensokyo.uk>
Diffstat (limited to 'container/container.go')
| -rw-r--r-- | container/container.go | 2 |
1 files changed, 1 insertions, 1 deletions
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 ( |