yubiuser cc078749eb Fix MD060 rule ...

Signed-off-by: yubiuser <github@yubiuser.dev>

2025-11-17 12:54:49 +01:00

..

blockingmode.md

Markdownlint: enable MD040 rule

2025-03-04 08:29:46 +02:00

cache_dump.md

Fix MD060 rule

2025-11-17 12:54:49 +01:00

compile.md

Update compiling documentation for FTL following the recent update in https://github.com/pi-hole/docker-base-images/pull/120

2025-09-21 09:48:42 +02:00

configfile.md

docs: update pihole.toml documentation

2025-10-27 21:08:34 +00:00

dns-cache.md

Typo corrections

2025-07-18 08:43:10 +10:00

dns-resolver.md

Typo corrections

2025-07-18 08:43:10 +10:00

dnsmasq_warn.md

Typo corrections

2025-07-18 08:43:10 +10:00

gdb.md

Rename ftldns/debugging -> ftldns/gdb for clarity

2024-11-12 09:33:28 +01:00

index.md

Upate markdown_extensions:

2022-12-11 14:55:26 +01:00

interfaces.md

Markdownlint: enable MD040 rule

2025-03-04 08:29:46 +02:00

package_dump.md

Markdownlint: enable MD040 rule

2025-03-04 08:29:46 +02:00

privacylevels.md

Upate markdown_extensions:

2022-12-11 14:55:26 +01:00

signals.md

After a report on Discourse, investigations have revealed that SIGRTMIN are defined differently in Debian (glibc-based) and Alpine (musl-based). Hence, sending signals relative to SIGRTMIN is going to be an issue on Debian as we build the pihole-FTL binaries on Alpine. Change the documentation to use fixed signals (instead of relative ones) to fix this. Signals relative to the constant SIGRTMIN have been added as there is a certain number ambiguity under glibc (see man 7 signals). However, this ambiguity does not exist in musl-based binaries.

2025-03-05 05:02:12 +01:00

valgrind.md

Markdownlint: enable MD040 rule

2025-03-04 08:29:46 +02:00

webserver.md

Add webserver documentation

2025-06-30 13:50:27 +02:00