Hi Richard, Richard Homonnai writes: > The default watchdog behaviour (which you get if you say N here) > is to stop the timer if the process managing it closes the file > /dev/watchdog. It's always remotely possible that this process > might get killed. If you say Y here, the watchdog cannot be > stopped once it has been started. > > That is exactly what I meant.
Hmm, I don't think this does what you think it does. The flag only applies to the case where /dev/watchdog is closed, as in was open and is now closed It can't be closed unless it is first opened, and the only thing that's going to open it is the userspace watchdog process. Looking at scx200_wdt.c, the nowayout parameter is only used in two places: - in scx200_wdt_release, when /dev/watchdog is closed - in scx200_wdt_notify_sys, when the system is being shut down > The name is quite a bad choose, but this is definitely it. It's a bit silly, but accurate, I think? It means that you can't escape from the watchdog timer just by killing the userspace process -- there's no way out. :-) > It says "if /dev/wdX is not open, don't start (or halt if already > started) the watchdog timer." Not quite. It only indicates what should happen when a process which had opened /dev/watchdog (or/dev/wdX if you prefer) closes it. If you look at scx200_wdt_init, it disables the watchdog timer at init time, and the timer is only enabled in scx200_wdt_open. > So, if you are in boot process, /dev/wd0 just sits there. And when > watchdogd gets started, then it is open. So this option ist what > helped me, and there were no false negatives yet :) Yes, but that applies regardless of how nowayout is set. Cheers, -Ted _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
