<div dir="ltr"><div dir="ltr">Hi Konstantin,<br><br>Just wanted to follow up on the removal of capability sys_time - <br><br>This change is rather disappointing, because it means that virtuozzo containers can no longer be used in the role they played in the past and the management will likely just order them replaced by VMware instances when it's time for hardware refresh. <br><br>Sure, it's not optimal to have multiple containers potentially adjusting the system time, but even if its a kludge, it was a very useful one. <br><br>Jake<br><br><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 16, 2019 at 8:59 AM jjs - mainphrame <<a href="mailto:jjs@mainphrame.com">jjs@mainphrame.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Konstantin,<div><br></div><div>With commercial Virtuozzo, we deployed containers to various lans, where each container served ntp, among other things.The host itself is isolated.</div><div>Removal of this capability brings about a dead end scenario. Is there some other way to accomplish the ntp server duties moving forward?<br><br>Jake</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 16, 2019 at 5:19 AM Konstantin Khorenko <<a href="mailto:khorenko@virtuozzo.com" target="_blank">khorenko@virtuozzo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 05/16/2019 02:29 PM, Nethub Online - Ming wrote:<br>
> Hi Konstantin,<br>
><br>
> It is because we want to setup a NTP server in CT, and then let other servers to update their system time via ntpdate from this CT. However after install NTP server in this CT, it<br>
> is unable to start NTP service.<br>
<br>
Hi again,<br>
<br>
thank you, the usecase is understandable.<br>
We usually just run ntp clients on all hosts and don't face with time unsync in Containers,<br>
it's only a matter of one-time configuration of ntp service...<br>
<br>
--<br>
Best regards,<br>
<br>
Konstantin Khorenko,<br>
Virtuozzo Linux Kernel Team<br>
<br>
> 於 2019年5月16日 下午5:25，"Konstantin Khorenko" <<a href="mailto:khorenko@virtuozzo.com" target="_blank">khorenko@virtuozzo.com</a> <mailto:<a href="mailto:khorenko@virtuozzo.com" target="_blank">khorenko@virtuozzo.com</a>>> 寫道：<br>
><br>
> On 05/15/2019 05:11 AM, Nethub Online - Ming wrote:<br>
> > Hi all,<br>
> ><br>
> > In OpenVZ 6 users guide ( <a href="https://download.openvz.org/doc/OpenVZ-Users-Guide.pdf" rel="noreferrer" target="_blank">https://download.openvz.org/doc/OpenVZ-Users-Guide.pdf</a> ), it allows me to change hardware node system time from container by command "vzctl set 101<br>
> > --capability sys_time:on --save"<br>
> ><br>
> > However I found that there is no such parameter for vzctl or prlctl under OpenVZ 7, may I know how to change hardware node system time from CT under OpenVZ 7?<br>
><br>
> Hi,<br>
><br>
> no way at the moment and you are the first who ask for it.<br>
> Why do you need it?<br>
> What it your usecase?<br>
><br>
> Thank you.<br>
><br>
> --<br>
> Best regards,<br>
><br>
> Konstantin Khorenko,<br>
> Virtuozzo Linux Kernel Team<br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a> <mailto:<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>
><br>
><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>
<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>
</blockquote></div>
</blockquote></div>