Carol Hebert wrote: > Regarding the question of why anyone would want to stop the daemon, I > guess there could be reasons why someone would want to stop it > (temporarily). Maybe they would want to change the > timeout/pretimeout/action/etc. settings during ipmi_watchdog module > insertion time (rather than through the ioctl interface)? Another idea > I'm wondering about is whether there might be an issue with the watchdog > timer running (and being poked) while a firmware upgrade was being > attempted or was underway? > In current 2.6 you can poke the settings directly through /sys/modules/ipmi_watchdog/parameters/... But that doesn't help you for now, I don't think.
And you don't really have to stop the watchdog to update the settings; you should be able to unload and load fast enough to avoid the timer going off. The firmware upgrade issue is a good reason I didn't think of. Yes, it's a bad idea to be poking the watchdog during that operation :). -Corey ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
