Well, that certainly is useful information and would alleviate my concerns with that.
-Mathew "When you do things right, people won't be sure you've done anything at all." - God; Futurama "We'll get along much better once you accept that you're wrong and neither am I." - Me On Tue, Oct 29, 2013 at 6:53 PM, Brandon Allbery <[email protected]>wrote: > On Tue, Oct 29, 2013 at 9:30 PM, Mathew Snyder <[email protected]>wrote: > >> The only problem I see with the onerror=panic option is that we don't >> necessarily want servers to reboot immediately. This would do us no good >> when the network to the storage backend is down. We'd end up having to >> reboot manually anyway in this scenario once the storage is back online and >> each VM is able to boot to its respective disk. >> > > There should be a sysctl option (kernel.panic) to control automatic reboot > on panic: 0 means don't reboot, otherwise it's a number of seconds to wait > after a panic before rebooting. > > -- > brandon s allbery kf8nh sine nomine > associates > [email protected] > [email protected] > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net >
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
