Hello again,
thank you all for your help. The problem is solved now.
The key points have been:
--> start ntp with -g
--> remove the lines including 127.127.1.* from leaf-nodes
Maybe it would be better to take orphan mode into account,
but at the moment I haven't enough understanding of this mod
On 2011-05-20, Richard B. Gilbert wrote:
> On 5/19/2011 12:08 PM, M. Giertzsch wrote:
>>
>>
>> Am 19.05.2011 17:55, schrieb Chris Albertson:
>>> On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch
>>> wrote:
>>>
Now if there is a powerfail, there is no guarantee that the server has
finished th
Richard wrote:
> NTPD needs something like thirty minutes before it is able to serve a
> reasonable facsimile of the correct time. It needs up to ten hours
> after startup to deliver the highest quality time that it is capable of.
Well, that's true for cold-start, with no drift file. But it's
On Thu, May 19, 2011 at 5:38 PM, Richard B. Gilbert
wrote:
> On 5/19/2011 12:08 PM, M. Giertzsch wrote:
>>
>>
>> Am 19.05.2011 17:55, schrieb Chris Albertson:
>>>
>>> On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch
>>> wrote:
>>>
Now if there is a powerfail, there is no guarantee that the serve
On 5/19/2011 12:08 PM, M. Giertzsch wrote:
Am 19.05.2011 17:55, schrieb Chris Albertson:
On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch
wrote:
Now if there is a powerfail, there is no guarantee that the server has
finished the boot
before the clients have. In this case the time will not be sy
M. Giertzsch wrote:
> The servers configuration is:
>restrict default notrap nomodify nopeer noquery
-^^^
>restrict 127.0.0.1
>driftfile /var/status/ntp.drift
>pidfile /var/run/ntpd.pid
>server 127.127.1.1
>fudge 127.127.1.1 st
On May 19, 2011, at 2:53 PM, Hal Murray wrote:
>> By default, ntpd will not try to correct a clock which is insanely far off.
>> The -g flag can be used to change this; otherwise run ntpdate -b at boot
>> to get the clock close and then run ntpd afterwards to keep the clock in
>> sync.
>
> Runnin
In article <35fcd513-e8ea-4feb-a33b-6d47d6556...@mac.com>,
Chuck Swiger writes:
>On May 19, 2011, at 10:01 AM, M. Giertzsch wrote:
>> To run into the problem that the client is not syncing to the server I
>> --> stopped the NTP service on both client and server
>> --> changed the time on the clie
M. Giertzsch wrote:
> To run into the problem that the client is not syncing to the server I
> --> stopped the NTP service on both client and server
> --> changed the time on the client back to january of 1975
> --> started the NTP service on the client
> --> started the NTP service on the server
On 2011-05-19, M. Giertzsch wrote:
> This is of course true, I can't say that that one server serves the
> correct time. But in a closed environment I can't guarantee that even
> when using more servers. If real time is needed I'm in need of a GPS
> module or something like this.
The GPS gives y
M. Giertzsch wrote:
But hmm, still it seems to me that the client does not sync when
finished booting
before the server does. What about that iburst mentioned in my recent
post and may it be that
I have to be more patient waiting for the next poll (but I waited half
an hour).
What is your cl
On May 19, 2011, at 10:01 AM, M. Giertzsch wrote:
> To run into the problem that the client is not syncing to the server I
> --> stopped the NTP service on both client and server
> --> changed the time on the client back to january of 1975
> --> started the NTP service on the client
> --> started t
Am 18.05.2011 11:57, schrieb M. Giertzsch:
Hello together,
I want to synchronise a local network and there is no uplink to the
outside world.
So I have one dedicated ntp server and all other devices are client of
this server.
Now if there is a powerfail, there is no guarantee that the server
You shouldn't use 127.127.1.1. as local backup clock.
Just set "tos orphan 13", remove 127.127.1.1 and orphan server would give
it's time to clients.
Then, you can remove "restrict" clauses and see what's happening - I think
you don't need them.
Without restrict you could use ntpq tools to query s
Am 19.05.2011 17:52, schrieb M. Giertzsch:
Am 19.05.2011 16:01, schrieb Heiko Gerstung:
Hi,
Am 18.05.2011 11:57, schrieb M. Giertzsch:
Hello together,
I want to synchronise a local network and there is no uplink to the
outside world.
So I have one dedicated ntp server and all other devices
Am 19.05.2011 17:55, schrieb Chris Albertson:
On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch wrote:
Now if there is a powerfail, there is no guarantee that the server has
finished the boot
before the clients have. In this case the time will not be synced.
If the clients are running
On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch wrote:
> Now if there is a powerfail, there is no guarantee that the server has
> finished the boot
> before the clients have. In this case the time will not be synced.
If the clients are running the standard ntpd they will continue poling
"forever"
Am 19.05.2011 16:01, schrieb Heiko Gerstung:
Hi,
Am 18.05.2011 11:57, schrieb M. Giertzsch:
Hello together,
I want to synchronise a local network and there is no uplink to the outside
world.
So I have one dedicated ntp server and all other devices are client of this
server.
Now if there
Hi,
Am 18.05.2011 11:57, schrieb M. Giertzsch:
> Hello together,
>
> I want to synchronise a local network and there is no uplink to the outside
> world.
> So I have one dedicated ntp server and all other devices are client of this
> server.
> Now if there is a powerfail, there is no guarantee
Hello together,
I want to synchronise a local network and there is no uplink to the
outside world.
So I have one dedicated ntp server and all other devices are client of
this server.
Now if there is a powerfail, there is no guarantee that the server has
finished the boot
before the clients ha
20 matches
Mail list logo
