Updating linux time dating direct affinity log in
16-Dec-2019 16:35
I think you may be mis-understanding the exact degree to which this issue affects NTP clients in a virtualized environment.In my experience on a virtualized system on a Xen host (such as our setup at Rackspace Cloud) the inaccuracy inherited by not having a dedicated system clock to process the interrupts amounts to fractions of a second, even on highly loaded systems.Most servers are probably automatically configured to network time, but if you want to set it up for yourself, or want to change the servers that you are syncing to, here’s the quick article that shows you how to do it.Since I had to do this earlier today, I decided it would make a lot of sense to write it down for the next time that I need to do it. First, you’ll need to install NTP if it isn’t already installed.
I pointed them to this thread, and some other documentation indicating that maybe the CPU allocation would cause a timing problem.
The location of update pages is specified in /etc/apt/(repositories).