Hi Alejandro, > I have a doubt about the use of internal timer to reset the wdt when the > watchdog device was closed from userspace and it doesn't support > stopping the wdt. > I think, in my modest opinion, that if the watchdog device was closed at > userspace it means that something is wrong at userspace and the system > needs to be rebooted. No. the reason why magic_close was introduced in the past is because there was a need to be able to tell the driver that it could correctly stop. For instance for maintenance work, where the watchdog device should NOT reboot the system during the maintenance. So the reason why we sent that magic char is because we want to tell the driver that a watchdog daemon will stop working. In that case you do need that timer. > I think that the internal timer can be useful in the following scenario: > If an user reboot the system, then the internal timer must ensure that > the watchdog didn't reset the system during the reboot process and it > send ticks to the wdt until the user/clean reboot process get finished. > Maybe a reboot notifier can be used to detect when the user reboot the > system manually. If a system is rebooted then the watchdog device is also resetted. So until you start the watchdog, it will not be activated... Kind regards, Wim. -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
