Hi Brian,

> When I integrated NTP v4 into Nevada, I included a test in the startup
> method to check if the service was running in the global zone and to fail
> if it were not. This seemed reasonable because the privs necessary for NTP
> to control the system clock are only available in the global zone.
> However, I forgot to take into account the fact that extra privs can now be
> added to the local zones, which would allow ntpd to run in a local
> zones. Furthermore, customers have expressed a desire to run ntpd in local
> zones for various reasons.

great, thanks for doing this.  It had been on my agenda for quite some
time, but ntp work has fallen behind lately ;-(

> I think that is the best we can reasonably do. If anybody has any better
> ideas, or comments on the "right way" to do this, please let me know.

My suggestion would be to check for this problem in the kernel,
i.e. remember the last caller to ntp_adjtime(2) and reject another one
if thr other process is still running, irrespective of zone.


Rainer Orth, Center for Biotechnology, Bielefeld University
zones-discuss mailing list

Reply via email to