summaryrefslogtreecommitdiff
path: root/libpod/shutdown/handler.go
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2021-08-17 12:10:20 +0200
committerValentin Rothberg <rothberg@redhat.com>2021-08-17 12:10:20 +0200
commitfe2be7f886ac3be68a1899eeb63f756d6fe3d744 (patch)
tree6b43476231046f0f57a63ed2822f0bbe9a499f74 /libpod/shutdown/handler.go
parent8c228bdbd031e5930e6319e8fe25b3ff340919f3 (diff)
downloadpodman-fe2be7f886ac3be68a1899eeb63f756d6fe3d744.tar.gz
podman-fe2be7f886ac3be68a1899eeb63f756d6fe3d744.tar.bz2
podman-fe2be7f886ac3be68a1899eeb63f756d6fe3d744.zip
make sure that signal buffers are sufficiently big
Dealing with os.Signal channels seems more like an art than science since signals may get lost. os.Notify doesn't block on an unbuffered channel, so users are expected to know what they're doing or hope for the best. In the recent past, I've seen a number of flakes and BZs on non-amd64 architectures where I was under the impression that signals may got lost, for instance, during stop and exec. [NO TESTS NEEDED] since this is art. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'libpod/shutdown/handler.go')
-rw-r--r--libpod/shutdown/handler.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/libpod/shutdown/handler.go b/libpod/shutdown/handler.go
index 848b6729a..1e8a9ec3b 100644
--- a/libpod/shutdown/handler.go
+++ b/libpod/shutdown/handler.go
@@ -35,7 +35,7 @@ func Start() error {
return nil
}
- sigChan = make(chan os.Signal, 1)
+ sigChan = make(chan os.Signal, 2)
cancelChan = make(chan bool, 1)
stopped = false