From dda61e2029029d62f5876ebebba69900f46580c7 Mon Sep 17 00:00:00 2001 From: Frank Louwers Date: Tue, 1 Oct 2019 17:44:38 +0200 Subject: [PATCH] Typo. Thanks @phonedph1 --- pdns/pdns_recursor.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pdns/pdns_recursor.cc b/pdns/pdns_recursor.cc index b28d87005..94334b1bc 100644 --- a/pdns/pdns_recursor.cc +++ b/pdns/pdns_recursor.cc @@ -4088,9 +4088,9 @@ static int serviceMain(int argc, char*argv[]) For years, this was a safe assumption, but containers change that: in most (all?) container implementations, the application itself is running as pid 1. This means that sending signals to those applications, will not - be handled by default. Results might be "you container not responsing - when asking it to stop", or "ctrl-c" not working even when the app is - running in the foreground inside a container. + be handled by default. Results might be "your container not responsing + when asking it to stop", or "ctrl-c not working even when the app is + running in the foreground inside a container". So TL;DR: If we're running pid 1 (container), we should handle SIGTERM and SIGINT ourselves */ -- 2.40.0