<div dir="ltr">Hi Kyrill - <div><br></div><div>It sounds like this is unexpected, so I'll file a bug.</div><div><br></div><div>Regards,</div><div><br></div><div>Jake</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 30, 2016 at 4:14 PM, Kirill Kolyshkin <span dir="ltr"><<a href="mailto:kolyshkin@gmail.com" target="_blank">kolyshkin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I suggest to file a bug saying that ONBOOT flag in ctid.conf is not honored.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 30 June 2016 at 15:04, jjs - mainphrame <span dir="ltr"><<a href="mailto:jjs@mainphrame.com" target="_blank">jjs@mainphrame.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Scott,<div><br></div><div>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.</div><div><br></div><div>Jake</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 30, 2016 at 9:56 AM, Scott Dowdle <span dir="ltr"><<a href="mailto:dowdle@montanalinux.org" target="_blank">dowdle@montanalinux.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>Greetings,<br>
<br>
----- Original Message -----<br>
</span><span>> The containers we're expecting to start on boot are precisely those<br>
> which have "ONBOOT="yes" in their config files. And up until a few<br>
> updates ago, they always started on boot.<br>
<br>
</span>Well, that is news. I haven't tried to verify yet.<br>
<span><br>
<br>
> That said, this new behavior of suspending running containers on shutdown seems useful<br>
> though.<br>
<br>
</span>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:<br>
<br>
VE_STOP_MODE<br>
<br>
This from the vz.conf man page:<br>
<br>
VE_STOP_MODE=suspend|stop<br>
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.<br>
<div><div><br>
TYL,<br>
--<br>
Scott Dowdle<br>
704 Church Street<br>
Belgrade, MT 59714<br>
<a href="tel:%28406%29388-0827" value="+14063880827" target="_blank">(406)388-0827</a> [home]<br>
<a href="tel:%28406%29994-3931" value="+14069943931" target="_blank">(406)994-3931</a> [work]<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>