Re: Clock drift issues
Try running ntpd rather than one off ntpdate? I have plenty of physical machines that need this anyway. Vince On 30/05/2011 05:41, Alex wrote: Hi Guys, Running 8.2-RELEASE/amd64 as the operating system on my VPS. Every couple of weeks I am finding myself having to log in and resync the clock as it's drifted (I am in Au (GMT+10)). Today again: srv# date Mon May 30 14:21:16 EST 2011 srv# /etc/rc.d/ntpdate start Setting date via ntp. 30 May 14:37:41 ntpdate[8207]: step time server 203.171.85.237 offset 958.736122 sec srv# date Mon May 30 14:37:43 EST 2011 - Is there any fix for this? Thanks, Alex. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Clock drift issues
Hi, The clock is Sync'd though, it should *stay* correct, right? So there is a bug? On Mon, 30 May 2011 09:39:06 +0100, Vincent Hoffman wrote: Try running ntpd rather than one off ntpdate? I have plenty of physical machines that need this anyway. Vince On 30/05/2011 05:41, Alex wrote: Hi Guys, Running 8.2-RELEASE/amd64 as the operating system on my VPS. Every couple of weeks I am finding myself having to log in and resync the clock as it's drifted (I am in Au (GMT+10)). Today again: srv# date Mon May 30 14:21:16 EST 2011 srv# /etc/rc.d/ntpdate start Setting date via ntp. 30 May 14:37:41 ntpdate[8207]: step time server 203.171.85.237 offset 958.736122 sec srv# date Mon May 30 14:37:43 EST 2011 - Is there any fix for this? Thanks, Alex. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Clock drift issues
On Mon, 30 May 2011, Alex wrote: The clock is Sync'd though, it should *stay* correct, right? So there is a bug? My experience is also that the clock is not stable on FreeBSD 8.X guest on Xen and KVM HVM. It is unusable as a ntp server for other hosts and I need to run ntpd to prevent the guest clock from drifting and jumping. Some times I get syslog messages about the time going backwards, which is probably related: calcru: runtime went backwards from 41668 usec to 35093 usec for pid 96767 (bash) I have not tried this with the CURRENT kernel (which has new and configurable event timer infrastructure by mav@). (Linux guests are fine for running ntp server within Xen KVM.) -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.com/ ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Clock drift issues
Hi Guys, Running 8.2-RELEASE/amd64 as the operating system on my VPS. Every couple of weeks I am finding myself having to log in and resync the clock as it's drifted (I am in Au (GMT+10)). Today again: srv# date Mon May 30 14:21:16 EST 2011 srv# /etc/rc.d/ntpdate start Setting date via ntp. 30 May 14:37:41 ntpdate[8207]: step time server 203.171.85.237 offset 958.736122 sec srv# date Mon May 30 14:37:43 EST 2011 - Is there any fix for this? Thanks, Alex. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
