Date: Wed, 13 Apr 2011 08:50:28 -0700 From: Tobias Oberstein <tobias.oberstein@tavendo.de> To: Martin Simmons <martin@lispworks.com>, "freebsd-emulation@freebsd.org" <freebsd-emulation@freebsd.org> Subject: AW: AW: AW: rc.d script for running multiple VirtualBox VMs from /etc/rc.conf Message-ID: <634914A010D0B943A035D226786325D422B76F94CA@EXVMBX020-12.exch020.serverdata.net> In-Reply-To: <201104131436.p3DEaPmO019975@higson.cam.lispworks.com> References: <634914A010D0B943A035D226786325D422B76F91CA@EXVMBX020-12.exch020.serverdata.net> <4DA4A6C7.6050803@FreeBSD.org> <634914A010D0B943A035D226786325D422B76F9205@EXVMBX020-12.exch020.serverdata.net> <4DA4AE8A.6020308@FreeBSD.org> <634914A010D0B943A035D226786325D422B76F9275@EXVMBX020-12.exch020.serverdata.net> <201104131436.p3DEaPmO019975@higson.cam.lispworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > In the meantime, I've implemented stop_cmd as synchronous (it does not > > return until VM is stopped) and also restart_cmd. > > > > I somehow works .. but there seems to be a watchdog in place: I get > > > > "watchdog timeout 30s expired ... shutodown NOW" > > > > Is it possible to override the 30s watchdog? >=20 > Maybe set rcshutdown_timeout (see man rc.conf)? Ah, ok. Thank you! It works .. Note: after reading up, above rc.conf variable is the "shutdown soft limit"= . There is also a "shutdown hard limit", which can be set kern.init_shutdown_timeout and which defaults to 120s. So when using rcshutdown_timeout > 120 one needs to set kern.init_shutdown_timeout >=3D rcshutdown_timeout also. http://people.freebsd.org/~rse/work/shutdown-timeout.txt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?634914A010D0B943A035D226786325D422B76F94CA>