From 05a9899b8647e8086ce803c1f40bfc9a9f3ee25f Mon Sep 17 00:00:00 2001 From: yubiuser Date: Mon, 21 Jul 2025 11:34:11 +0200 Subject: [PATCH] Add note about pihole-FTL sigrtmin Signed-off-by: yubiuser --- docs/ftldns/signals.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/ftldns/signals.md b/docs/ftldns/signals.md index a14049c..3b2fdaa 100644 --- a/docs/ftldns/signals.md +++ b/docs/ftldns/signals.md @@ -33,7 +33,16 @@ When FTL receives a `SIGHUP`, it clears the entire DNS cache, and then While `SIGHUP` updates/flushes almost everything, such a massive operation is often not necessary. Hence, we added several small real-time signals available for fine-grained control of what FTL does. When you see `SIGHUP` as a "big gun", the real-time signals are rather the "scalpel" to serve rather specific needs. -Real-time signals are not guaranteed to have the same number on all operating systems as the value of the constant `SIGRTMIN` may vary. For the signals described below, we recommend using the exact signal number described in the parentheses, e.g., real-time signal 0 (35) can be sent like: + +!!! warning "Real-time signals vary" + Real-time signals are not guaranteed to have the same number on all operating systems as the value of the constant `SIGRTMIN` may vary. + You can check the value on your system with + + ```bash + pihole-FTL sigrtmin + ``` + +For the signals described below, we recommend using the exact signal number described in the parentheses, e.g., real-time signal 0 (assuming `RTMIN=35`) can be sent like: ```bash sudo pkill -SIG35 pihole-FTL