watchdog: clarify that we set the *watchdog* timeout
authorLennart Poettering <lennart@poettering.net>
Thu, 4 Apr 2024 07:59:00 +0000 (09:59 +0200)
committerLennart Poettering <lennart@poettering.net>
Thu, 4 Apr 2024 15:53:38 +0000 (17:53 +0200)
commit99a1ef8c9cdcb0fc15265533dae2bbd8f2d7a3a5
tree218db72002f73c9847f804170693df3217cab6f3
parent3cb618084a1bd5c7cb42822b4ce3dbd048e6bd24
watchdog: clarify that we set the *watchdog* timeout

This makes sure we mention the word "watchdog" in every log message
related to the watchdog.

Also, this uses the expression "hardware timeout" when referring to the
primary timeout of the watchdog, as opposed to the "pretimeout".

(Not ideal wording I know, but it's preexisting to some point, I just
continued it. I think it's OK though, in particular to underline the
difference to the software watchdog logic we implement via WATCHDOG= in
sd_notify().)

Fixes: #31662
src/shared/watchdog.c