unruh wrote:
If I recall correctly his problem was that he had 4 outside sources plus
the local time. Then something disconnected him from those outside
sources for a long time ( hours) After that was fixed, the system never
again went back to those outside sources-- gave zero reachability even
On 2010-11-08, David Woolley wrote:
> Stephen Vaughan wrote:
>> Connectivity is fine to the ntp servers, if I restart ntpd it starts syncing
>> with an external clock immediately. This article could be the fix:
>>
>> http://www.novell.com/coolsolutions/feature/15345.html
>
> This advises some ve
Hello,
I want to employ the AutoKey method of securing NTP.
Basically, I want one host that would act as an NTP client of an
external NTP server, talking AutoKey. This NTP client is to become the
NTP server for other hosts on the intranet. All these hosts are behind
a corporate firewall and are v
Chuck Swiger wrote:
> Anyway, from http://en.wikipedia.org/wiki/Usage_share_of_operating_systems
>
> "Web client stats suggest that Microsoft Windows has about an
> 88% share, Apple Mac OS 7% and Linux 1%.
> The correlation between desktop share and web client share
> is being increasingly ch
Alright, I'll give it a miss then. We'll look into removing the locl clock.
Cheers,
Stephen
-Original Message-
From: questions-bounces+stephen.vaughan=blackboard@lists.ntp.org
[mailto:questions-bounces+stephen.vaughan=blackboard@lists.ntp.org] On
Behalf Of Steve Kostecke
Sent:
On 2010-11-08, Stephen Vaughan wrote:
> Yep it does work, I think that article I just posted is the fix.
That should go in the Wiki.
--
Steve Kostecke
NTP Public Services Project - http://support.ntp.org/
___
questions mailing list
questions@lists.
On 2010-11-08, Stephen Vaughan wrote:
> Yep it does work, I think that article I just posted is the fix.
Actually, that belongs in the Wiki as an example of what _not_ to do.
"burst" makes your ntpd poll the remote time server 8 times in rapid
sucession at each poll interval. Use of 'burst' aga
Stephen Vaughan wrote:
Connectivity is fine to the ntp servers, if I restart ntpd it starts syncing
with an external clock immediately. This article could be the fix:
http://www.novell.com/coolsolutions/feature/15345.html
This advises some very anti-social practice, namely using burst on
pub
Yep it does work, I think that article I just posted is the fix.
Cheers,
Stephen
-Original Message-
From: Kevin Oberman [mailto:ober...@es.net]
Sent: Monday, November 08, 2010 2:55 PM
To: Stephen Vaughan
Cc: questions@lists.ntp.org
Subject: Re: [ntp:questions] Local clock - sync issue
>
Connectivity is fine to the ntp servers, if I restart ntpd it starts syncing
with an external clock immediately. This article could be the fix:
http://www.novell.com/coolsolutions/feature/15345.html
Cheers,
Stephen
-Original Message-
From: questions-bounces+stephen.vaughan=blackboard..
Is anyone able to shed some further light on this issue? I plan to
remove the LOCAL clock from ntp's configuration, but I'm still keen to
know why it's defaulting to the LOCAL clock once network connectivity is
down, and then ignoring any of the public NTP servers configured when
network connec
On Mon, Nov 8, 2010 at 3:54 PM, Miroslav Lichvar wrote:
> No, it really is about the 500ppm limit. In loopstats is only the
> measured clock frequency, it doesn't contain the phase
> adjustments which are included in the adjtime() argument.
Miroslav shared the following patch with me, which limit
> From: Stephen Vaughan
> Date: Mon, 8 Nov 2010 10:15:30 -0700
>
> Hi All,
>
> Is anyone able to shed some further light on this issue? I plan to remove the
> LOCAL clock from ntp's configuration, but I'm still keen to know why it's
> defaulting to the LOCAL clock once network connectivity is
Hi All,
Is anyone able to shed some further light on this issue? I plan to remove the
LOCAL clock from ntp's configuration, but I'm still keen to know why it's
defaulting to the LOCAL clock once network connectivity is down, and then
ignoring any of the public NTP servers configured when networ
On Mon, Nov 08, 2010 at 03:09:57PM +, David L. Mills wrote:
> It is not an issue of limiting the slew rate to less than
> 500 PPM, as that is in fact the result shown in the looopstats
> trace.
No, it really is about the 500ppm limit. In loopstats is only the
measured clock frequency, it does
Dave,
Notice toward the end of the calibration period adjtime() is called with
only a small offset, so issues like the slew rate and residual offset
are moot. Those calls should minimize the residual and the actual clock
time should be within the measuement offset. Apparentyl, at least the
Fr
On Mon, Nov 08, 2010 at 05:30:22AM +, Dave Hart wrote:
> On Mon, Nov 8, 2010 at 05:14 UTC, David L. Mills wrote:
> > At this point I am prepared to
> > abandon the mission entirely, as I don't want to get bogged down with the
> > specifics of each idiosyncratic operating system. Accordingly, I
17 matches
Mail list logo
