Mark Johanson <mjohan...@a2hosting.com> writes: > Just started seeing this myself. Is there wa way to force a stop instead > of suspend?
If you look at /etc/init.d/vz there is suspend and then a stop at the end. Why is suspend done first is beyond me. I guess you could disable it by changing the line stages="suspend stop" to stages="stop" in stop_ves() function Interestingly enough, suspend doesnt work at all currently for me on RHEL6 kernel, it just says in the syslog Nov 28 15:27:37 free-3 kernel: [14278.117357] CT: checkpointing not supported yet for hidden pid namespaces. so it actually does a stop and it doesn't hurt anything as far as I can tell. > On Tue, 2012-11-20 at 11:10 -0700, Ruslan Dautkhanov wrote: >> When HN reboots, it suspends all CTs, and after reboot complete - >> resumes them back up. >> Is any way to switch off this feature? >> It takes many minutes to suspend a database CT, and then many minutes >> to resume it back. >> It is *way* faster to just shut down database normally and then start >> it up (withing 10-15 seconds or so). >> >> If it's not possible to do on per-container base, I would disable this >> feature globally. >> >> Any way to accomplish this? >> >> Thanks, >> >> Ruslan >> >> _______________________________________________ >> Users mailing list >> Users@openvz.org >> http://lists.openvz.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@openvz.org http://lists.openvz.org/mailman/listinfo/users
