I suggest to file a bug saying that ONBOOT flag in ctid.conf is not honored.
On 30 June 2016 at 15:04, jjs - mainphrame <j...@mainphrame.com> wrote: > Hi Scott, > > Thanks for the background. On OVZ 7 at least, this seemed to be a change > in default behavior. Perhaps just a consequence of starting my OVZ 7 > involvement with the early pre-releases. > > Jake > > On Thu, Jun 30, 2016 at 9:56 AM, Scott Dowdle <dow...@montanalinux.org> > wrote: > >> Greetings, >> >> ----- Original Message ----- >> > The containers we're expecting to start on boot are precisely those >> > which have "ONBOOT="yes" in their config files. And up until a few >> > updates ago, they always started on boot. >> >> Well, that is news. I haven't tried to verify yet. >> >> >> > That said, this new behavior of suspending running containers on >> shutdown seems useful >> > though. >> >> That isn't new behavior. They actually made that the default (I believe) >> a few years back. See the following setting in /etc/vz/vz.conf: >> >> VE_STOP_MODE >> >> This from the vz.conf man page: >> >> VE_STOP_MODE=suspend|stop >> If the value of this parameter is set to suspend or not set at all, >> vz initscript called with stop argument will try to suspend the running >> containers, instead of stopping them. Suspended containers when will be >> restored on vz start. This feature usually helps to decrease the reboot >> time. If a container fails to suspend, it will be stopped anyway. >> >> TYL, >> -- >> Scott Dowdle >> 704 Church Street >> Belgrade, MT 59714 >> (406)388-0827 [home] >> (406)994-3931 [work] >> _______________________________________________ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users >> > > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > >
_______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users