Is it worth specifically mentioning somewhere that this implies a systemd boot?

Nitpick: the description refers to the 'OS' but it really means that the systemd watchdog daemon will kick the wdog. When I read the initial description I initially thought there was a kernel driver that cancelled the wdog once the OS (ie the kernel) had booted. Semantic difference, but maybe worth clarifying.

Great feature 👍

Nitpick: the description refers to the 'OS' but it really means that the systemd watchdog daemon will kick the wdog. When I read the initial description I initially thought there was a kernel driver that cancelled the wdog once the OS (ie the kernel) had booted. Semantic difference, but maybe worth clarifying.

Is it worth specifically mentioning somewhere that this implies a systemd boot?

Nitpick: the description refers to the 'OS' but it really means that the systemd watchdog daemon will kick the wdog. When I read the initial description I initially thought there was a kernel driver that cancelled the wdog once the OS (ie the kernel) had booted. Semantic difference, but maybe worth clarifying.

Great feature 👍

It does say ""

Is it worth specifically mentioning somewhere that this implies a systemd boot?

Nitpick: the description refers to the 'OS' but it really means that the systemd watchdog daemon will kick the wdog. When I read the initial description I initially thought there was a kernel driver that cancelled the wdog once the OS (ie the kernel) had booted. Semantic difference, but maybe worth clarifying.

Great feature 👍

I might get Cursor to rewrite
"On Raspberry Pi OS Bookworm, the RuntimeWatchdogSec parameter is not set by default. This means that, unless you explicitly configure it in /etc/systemd/system.conf or a drop-in, the kernel watchdog will only be active during system startup (open timeout), and not during normal runtime."