Quoting Rob (nom...@example.com):
What is actually wrong with running ntpdate to initially sync a clock?
The problem is that you give the clock an initial kick that ntpd does
not know about, and it tends to have problems correcting that.
This sometimes results in the problems you are seeing.
Sander Smeenk ssme...@freshdot.net wrote:
Quoting Terje Mathisen (terje.mathi...@tmsw.no):
a) You should not run ntpdate, instead you use the -q option to ntpd to
handle any initial time steps.
What is actually wrong with running ntpdate to initially sync a clock?
Why is the ntpdate.exe
On Wed, 21 Jan 2015 09:24:40 +, Sander Smeenk wrote:
Hi,
I seek your help in strange timekeeping issues on Windows 2008r2 VMs
running on a Linux QEMU/KVM host. The clock drifts like a boat in a storm
at high sea and NTPD is giving me very very strange results.
From our internal wiki:
Quoting detha (de...@foad.co.za):
From our internal wiki:
Timekeeping sucks in windows, more so in VMs. What seems to improve things
a bit in kvm/qemu VMs is adding the ffg to the machine definition:
Thanks a bundle! I will definately play with this on my test VMs.
--
| Daylight savings
Paul writes:
On Wed, Jan 21, 2015 at 9:48 AM, Sander Smeenk ssme...@freshdot.net wrote:
What is actually wrong with running ntpdate to initially sync a clock?
It's no longer needed, as best as I can tell. 'ntpd -g' will accept any
size initial correction and keep running. If you really
On 21/01/2015 17:43, Rob wrote:
[]
I know on VMware it works OK, but for Windows that OK is never nearly
as good as for Linux. A Linux system will remain within a few ms, for
Windows 60ms is not bad at all.
[]
Timekeeping for a Windows XP VMware virtual machine, hosted on a Windows
8.1
Rob writes:
Sander Smeenk ssme...@freshdot.net wrote:
What is actually wrong with running ntpdate to initially sync a
clock? Why is the ntpdate.exe binary provided when 'we' shouldnt use
it? Keep in mind that i 'just want to get to seconds accuracy'
before i start ntpd.
The problem is
Sander Smeenk writes:
Quoting Rob (nom...@example.com):
What is actually wrong with running ntpdate to initially sync a clock?
The problem is that you give the clock an initial kick that ntpd does
not know about, and it tends to have problems correcting that.
This sometimes results in
On 2015-01-21, Mike Cook michael.c...@sfr.fr wrote:
Ceux qui sont pr??ts ?? abandonner une libert?? essentielle pour obtenir une
petite et provisoire s??curit??, ne m??ritent ni libert?? ni s??curit??.
Benjimin Franklin
Le 21 janv. 2015 ?? 23:40, Harlan Stenn st...@ntp.org a ??crit :
Rob
Ceux qui sont prêts à abandonner une liberté essentielle pour obtenir une
petite et provisoire sécurité, ne méritent ni liberté ni sécurité.
Benjimin Franklin
Le 21 janv. 2015 à 23:40, Harlan Stenn st...@ntp.org a écrit :
Rob writes:
Sander Smeenk ssme...@freshdot.net wrote:
What is
On Wed, Jan 21, 2015 at 5:24 PM, Harlan Stenn st...@ntp.org wrote:
What is missing? We thought we caught all of the useful cases.
I made a small error. I meant ntpq and ntpd.
ntpdate -d
ntpdc fudge (admittedly that's not a query)
___
questions
On Wed, Jan 21, 2015 at 6:00 PM, Mike Cook michael.c...@sfr.fr wrote:
I don't have a free client to test this on, but I believe that by
default ntpdate will SLEW the clock
Yes, even the most cursory grep of ntpdate shows adjtime and slewing. The
-b and -B flags provide coarse controls.
Paul writes:
On Wed, Jan 21, 2015 at 5:24 PM, Harlan Stenn st...@ntp.org wrote:
What is missing? We thought we caught all of the useful cases.
I made a small error. I meant ntpq and ntpd.
ntpdate -d
That's covered. See
http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate
ntpdc
Paul writes:
On Wed, Jan 21, 2015 at 5:40 PM, Harlan Stenn st...@ntp.org wrote:
... I'm not aware of anything on either Windows or Unix that would
cause any applied immediate adjustment to have *any* residual affect
on ntp.
Well ... at least under Linux if ntpdate calls adjtime and then
On Wed, Jan 21, 2015 at 10:17 PM, Harlan Stenn st...@ntp.org wrote:
ntpdate -d
That's covered. See
http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate
I may be abusing ntpdate but ntpd -q -d (but sets the clock!) is not the
same as ntpdate -d which explicitly doesn't set the clock.
Paul writes:
--001a11c22f2e2c050d353eb6
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Jan 21, 2015 at 10:17 PM, Harlan Stenn st...@ntp.org wrote:
ntpdate -d
That's covered. See
http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate
I may be abusing ntpdate but ntpd
On Wed, Jan 21, 2015 at 5:40 PM, Harlan Stenn st...@ntp.org wrote:
... I'm not aware of anything on either Windows or Unix that would cause
any
applied immediate adjustment to have *any* residual affect on ntp.
Well ... at least under Linux if ntpdate calls adjtime and then another
program
Quoting Harlan Stenn (st...@ntp.org):
The time values are in milliseconds, not seconds.
Yes, that's right, my bad. :(
But that's not the point, really.
The offets keep increasing and increasing up to the point
where ntpd.exe drops all the servers and sync_ntp flag is lost.
The exact same ntp
The time values are in milliseconds, not seconds.
H
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
Hi,
I seek your help in strange timekeeping issues on Windows 2008r2 VMs
running on a Linux QEMU/KVM host. The clock drifts like a boat in a
storm at high sea and NTPD is giving me very very strange results.
The W32Time service (Windows' own 'NTP daemon') is switched off, as is
the Network Time
On 1/21/2015 2:10 AM, Mike Cook wrote:
And one of the reasons why a significant portion of the computing
community wants to get rid of leap seconds. A coverup for bad
engineering practices.
That's right. Instead of recognizing that the world rotates on it's own,
they want to change reality so
Quoting Terje Mathisen (terje.mathi...@tmsw.no):
a) You should not run ntpdate, instead you use the -q option to ntpd to
handle any initial time steps.
What is actually wrong with running ntpdate to initially sync a clock?
Why is the ntpdate.exe binary provided when 'we' shouldnt use it?
Keep
Sander Smeenk schrieb:
Quoting Harlan Stenn (st...@ntp.org):
The time values are in milliseconds, not seconds.
Yes, that's right, my bad. :(
But that's not the point, really.
The offets keep increasing and increasing up to the point
where ntpd.exe drops all the servers and sync_ntp flag is
On Wed, Jan 21, 2015 at 9:48 AM, Sander Smeenk ssme...@freshdot.net wrote:
What is actually wrong with running ntpdate to initially sync a clock?
Nothing. The party line is that ntpdate and ntpdc are deprecated. I do
hope that ntpq eventually incorporates all the features (I care about) of
24 matches
Mail list logo
