Valentin Rothberg fe2be7f886 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>		2021-08-17 12:10:20 +02:00
..
rootless.go	rootless: improve automatic range split	2021-05-05 18:03:10 +02:00
rootless_linux.c	rootless: avoid zombie process on first launch	2021-07-29 11:07:17 +02:00
rootless_linux.go	make sure that signal buffers are sufficiently big	2021-08-17 12:10:20 +02:00
rootless_test.go	rootless: improve automatic range split	2021-05-05 18:03:10 +02:00
rootless_unsupported.go	validate fds --preserve-fds	2020-08-04 15:09:17 -04:00