Bug#353053: watchdog: this needs to be resolved for xen when many domains need to be shut down

2007-02-12 Thread Michael Meskes
On Fri, Feb 09, 2007 at 09:42:26PM +1100, James Harper wrote: I thought of this as well... one at K01 and one at K99. K01 would create /etc/watchdog/shutdown, which watchdog would notice and not do any further network or process checks. K99 would actually stop the process. The startup script

Bug#353053: watchdog: this needs to be resolved for xen when many domains need to be shut down

2007-02-09 Thread Michael Meskes
On Fri, Feb 09, 2007 at 03:03:33PM +1100, James Harper wrote: Would it be possible for watchdog to detect a change to runlevel 0 or 6, and simply stop doing the checks which become unreliable once a shutdown has started? This behaviour could be controlled by a config option if necessary. And

Bug#353053: watchdog: this needs to be resolved for xen when many domains need to be shut down

2007-02-09 Thread James Harper
On Fri, Feb 09, 2007 at 03:03:33PM +1100, James Harper wrote: Would it be possible for watchdog to detect a change to runlevel 0 or 6, and simply stop doing the checks which become unreliable once a shutdown has started? This behaviour could be controlled by a config option if necessary.

Bug#353053: watchdog: this needs to be resolved for xen when many domains need to be shut down

2007-02-08 Thread James Harper
Package: watchdog Version: 5.2.6-6 Followup-For: Bug #353053 I'm having a problem where xen needs an unknown amount of time to shut down the virtual machines before it can shut down itself, which means shutting down watchdog when nowayout has been set causes a premature reboot. Would it be