Hi, I'm looking into what it would take to write a watchdog daemon and am trying to put together a list of requirements. I guess the first thing I need to know is whether anyone else is currently working on an ipmi watchdog daemon? If anyone on this mailing list is currently working on such a daemon, please let me know.
The next question is (assuming an ipmi watchdog daemon isn't already in the works by someone): where would be the best place for such a daemon to reside? I think that including it with ipmitool might be the right place, since that's where ipmievd lives. Please let me know if you disagree and feel it belongs in the OpenIPMI library or elsewhere instead. I thought I'd also start discussing requirements and let those in this forum help decide what are the correct set of features/functionality. Please respond if you have any comments/opinions/questions on any of these points or if you have others you would like to have added to the list. Thank you very much for your help, Carol Hebert ------------------------------------------------------ IPMI Watchdog Daemon Requirements/functionality: 1.) We probably want to have the daemon work strictly in-band (at least for the first go-round). The open ipmi_watchdog driver appears to have a great ioctl interface for watchdog timer manipulation and reset. Also, it seems like users won't want network latency or problems to possibly cause their boxes to be reset as would probably be the risk with an out-of-band interface. 2.) We probably want to allow the user to set possible parameters on the command line when starting the daemon (timeout, pre-timeout, action, pre-action, operation, start now, no way out). These settings should over-ride any settings made via ipmi.init/ipmi.sysconf. There should also be some default values for most of these for parameters where neither the init script nor the daemon were made to explicitly set the parameter values. 3.) The daemon would first check to make sure the timer wasn't already in-use (ipmi_open() does this) and then just basically set up the watchdog as per the parameter settings to execute the behaviors set via the various parameters. The daemon would send a periodic keepalive poke to reset the timer (available via ipmi_ioctl() ) and would also provide a signal handler to cleanly stop the watchdog timer in case the daemon terminated so the box wouldn't get reset because the watchdog daemon died in an otherwise healthy system. The signal handler would also free up the timer for use by another app (ipmi_close() does this for us). 4.) We could include pidfile support for the watchdog daemon but is that something we need? 5.) Other functionality? ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
