SWWDOG(4)

πŸ“¦ version 11.0, in nixpkgs unstable

πŸ’– swwdog(4) β€” software watchdog timer πŸ’–

okay bestie, welcome to the swwdog(4) page from the Kernel Interfaces Manual. this is the software watchdog timer, and it's lowkey the kernel's "are you still there??" bestie. no cap. ✨

🌸 NAME 🌸

swwdog β€” software watchdog timer. that's the whole name, periodt. πŸ’…

✨ SYNOPSIS ✨

pseudo-device swwdog

πŸŽ€ DESCRIPTION πŸŽ€

okay so the swwdog driver provides a software watchdog timer that works with wdogctl(8). if the timer expires, the system reboots if the boolean variable swwdog_reboot is true; otherwise, the system will panic. swwdog_reboot is accessible as the sysctl(8) variable hw.swwdog.reboot and defaults to false. 😭

The default period of swwdog is 60 seconds. yes, a whole minute β€” the watchdog is patient, but not that patient. πŸ’…

As with other watchdog timers, the swwdog driver prevents a system from suspending when the watchdog is armed. so if the watchdog is armed, the system is not going to sleep on you. periodt. 🫢

πŸ”₯ SEE ALSO πŸ”₯

πŸ‘‘ HISTORY πŸ‘‘

The swwdog driver was written by Steven M. Bellovin. iconic author behavior, honestly. 🫢

πŸ’€ BUGS πŸ’€

  • Only one watchdog timer can be active at any given time. (Arguably, this is a bug in the watchdog timer framework.) Therefore, only a single instance of the swwdog device can be created. so yeah, one at a time, bestie.
  • Kernel tickle mode is useless with swwdog and arguably should be rejected, since both it and this driver rely on the same callout mechanism; if one is blocked, almost certainly the other is as well.
  • The alarm option to wdogctl(8) isn't implemented.

mwah πŸ’‹ β€” this page is from Debian, dated June 8, 2011. hope that helped bestie 🫢✨

πŸ“¦ where this page comes from