Zitat von Klaus Hartnegg <[email protected]>:
Am 25.03.2014 08:21, schrieb col:
a few weeks ago i spun up an NTP server using a droplet (VPS) with
DigitalOcean. it's $5 ($5!!!) a month for a 512MB instance
This is probably one of many virtual machines that run on the same
hardware. This could make the clock run very discontinual. Certainly
great for many applications, but maybe suboptimal for ntp, that
should run directly on the hardware.
It depends if you use container or full virtual hosts. With typical
VPS you have a shared kernel and you are not allowed to set the
hardware clock or the kernel clock from inside the container. If the
host you are running on is synced with ntp this doesn't matter and ntp
happily distributes the host time. The downside is that ntpd run as
root in this case because it don't get the sys_time capability. If you
use full virtualisation you are on the trouble side because the
virtual system think it is able to access the clock alone but the
hypervisor actually only create a virtual clock with ever changing
precision.
Regards
Andreas
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
