On 10/07/14 03:07, vothanhhun...@gmail.com wrote:
After 2 hours it can sync now but I would expect it sync every 15
minutes because my program need precision time.
To speed up initial sync use iburst.
Your non-standard minpoll is contributing to the slow synchronisation.
However note that,
On Thursday, July 10, 2014 10:49:55 AM UTC+7, William Unruh wrote:
On 2014-07-10, vothanhhun...@gmail.com vothanhhun...@gmail.com wrote:
On Thursday, July 10, 2014 3:53:42 AM UTC+7, David Woolley wrote:
On 09/07/14 18:30, E-Mail Sent to this address will be added to the
On 09/07/2014 18:45, Paul wrote:
[]
However you're showing a bias which steers away from a better
solution, not needing the overhead of fully-featured NTPd isn't a
defect it's an advantage.
Simply that different folk have different needs.
You later say: It's a Reference Clock not an instance
On 10/07/2014 08:39, David Woolley wrote:
[]
As others have noted, precision time means widely differing things to
different people, ranging from the unachievable to cases where ntpd is
overkill. Many people would have a definition of precision time which
is unachievable on Windows, as Windows
On 07/10/2014 10:24 AM, vothanhhun...@gmail.com wrote:
Thanks for your explaination. The reason I use NTP because I want my
computer clock have the same time as the server. It is always 1 or 2
minutes behind compare to the ntp server.
I admit that it *is* odd that ntpd doesn't change that
vothanhhun...@gmail.com wrote:
Hi all,
Currently, I am working with meinberg ntp and I can't sync with ntp server. I
have made rules that allow UDP port 123, turned off w32time and change to some
popular ntp server but there is no luck.
I have followed this FAQ:
On 7/9/2014 11:40 PM, Paul wrote:
On Wed, Jul 9, 2014 at 8:05 PM, Null wrote:
[stuff]
Please check the links provided. It would seem the most common
problem people have is not being able to think about a network
attached reference clock that uses NTP responses rather than PPS +
serial stream
On Thu, Jul 10, 2014 at 4:20 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
Simply that different folk have different needs.
This true but not nearly as much as people think. But yes different
folks have different needs. Despite that in the next sentence
You later say: It's a
On 2014-07-10 02:24, vothanhhun...@gmail.com wrote:
On Thursday, July 10, 2014 10:49:55 AM UTC+7, William Unruh wrote:
On 2014-07-10, vothanhhun...@gmail.com vothanhhun...@gmail.com wrote:
On Thursday, July 10, 2014 3:53:42 AM UTC+7, David Woolley wrote:
On 09/07/14 18:30, E-Mail Sent to this
On Thu, Jul 10, 2014 at 9:07 AM, Brian Utterback
brian.utterb...@oracle.com wrote:
You still have the keys problem. Keys authenticate the NTP server to the
client. How would you manage keys?
Are you asking if it supports autokey? It currently doesn't,
according to the doc there's one
On 7/10/2014 9:26 AM, Paul wrote:
On Thu, Jul 10, 2014 at 9:07 AM, Brian Utterback
brian.utterb...@oracle.com wrote:
You still have the keys problem. Keys authenticate the NTP server to the
client. How would you manage keys?
Are you asking if it supports autokey? It currently doesn't,
Brian Inglis wrote:
You can start ntpd with -g option which allows it to step your system
time once,
when it first starts; using iburst pool hk.ntp.pool.org iburst will
allow the
correct offset to be set within about 16s after startup. Thereafter it
will stay
within +/-128ms of UTC; after it has
On 10/07/2014 14:13, Paul wrote:
On Thu, Jul 10, 2014 at 4:20 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
Simply that different folk have different needs.
This true but not nearly as much as people think. But yes different
folks have different needs. Despite that in the
On Thu, Jul 10, 2014 at 10:17 AM, Brian Utterback
brian.utterb...@oracle.com wrote:
Well, at least it supports the one key and it is apparently changeable. But
NTP authentication is not mutual authentication, nor does it have anything
to do with entitlement of the client.
I spoke overly
On 2014-07-10, vothanhhun...@gmail.com vothanhhun...@gmail.com wrote:
On Thursday, July 10, 2014 10:49:55 AM UTC+7, William Unruh wrote:
On 2014-07-10, vothanhhun...@gmail.com vothanhhun...@gmail.com wrote:
On Thursday, July 10, 2014 3:53:42 AM UTC+7, David Woolley wrote:
On 09/07/14
On 10/07/14 09:23, David Taylor wrote:
although Windows can be kept within a millisecond,
But the uncertainty in the delay between real world events and
application programs reading the corresponding time is likely to be
rather larger.
(Also, at least the past, ntpd only compensated well
On 2014-07-10 08:43, Martin Burnicki wrote:
Brian Inglis wrote:
You can start ntpd with -g option which allows it to step your system
time once,
when it first starts; using iburst pool hk.ntp.pool.org iburst will
allow the
correct offset to be set within about 16s after startup. Thereafter it
17 matches
Mail list logo
