From e96c9ee36bcc4e7d79db8735c56e09632ad14a1e Mon Sep 17 00:00:00 2001 From: DL6ER Date: Wed, 12 May 2021 14:28:34 +0200 Subject: [PATCH] Add instructions to terminate and strip capabilities from FTL Signed-off-by: DL6ER --- docs/ftldns/valgrind.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/ftldns/valgrind.md b/docs/ftldns/valgrind.md index 0a1e793..f1bcb81 100644 --- a/docs/ftldns/valgrind.md +++ b/docs/ftldns/valgrind.md @@ -21,6 +21,22 @@ Problems like these can be difficult to find by other means, often remaining und Make sure to terminate any existing FTL process before starting FTL inside `valgrind`. +### Preparations + +You have to stop the regular `pihole-FTL` process before starting a `valgrind` debugging session: + +``` bash +sudo service pihole-FTL stop +``` + +Furthermore, you'll have to strip the networking capabilities from the binary using: + +``` bash +sudo setcap -r /usr/bin/pihole-FTL +``` + +They'll automatically be re-added when using `sudo service pihole-FTL start` next time. + ### Command We suggest the following one-liner to run `pihole-FTL` in `memcheck`: