> > On Tue, Nov 13, 2012 at 08:00:23PM -0500, Ben Cotton wrote:
> > On EC2 (as in many virt environments) the hardware clock source is actually
> > synced and running an ntpd service on the client is redundant.
> >
>
> <bikeshed=blue>
> They say it is .... but it is not always. I have had multiple cases
> in KVM and some in Xen where supposedly the clock is kept up but what
> you end up is actually watching time go backwards if you hit heavy
> load in IO or CPU or Mem. Of course if you run into hardware like
> that.. you can install it after your DB has gone poopsies.
> </bikeshed>
I've seen that happen as well. I found this by hitting the pause button on the guest IIRC. I just always use NTP to avoid the worry, but I agree NTP (whether ntpd or chronyd) belongs in @standard not @core.
--
John Florian
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
