[ntp:questions] need option to ignore 'leap not in sync error'

David Woolley david at ex.djwhome.demon.invalid
Thu Jan 16 08:27:14 UTC 2014

On 16/01/14 07:00, Sanal, Arjun (NSN - IN/Bangalore) wrote:

[Excessively long line re-wrapped.]

> The problem is when the master says that it is not suitable for
> synchronization, the client blades shouldn't reject it. If they, do
> all the blades will end up with different time.

Use orphan mode, or, if you really must, define a local clock driver on 
the master.  (NB never define a local clock driver on pure clients.)

Orphan mode is the preferred solution to time islands, but, if you have 
no redundancy in the server, and the system is otherwise OK without it, 
and it has multiple upstream servers synchronised to a common time 
source (typically UTC), you will get away with a high stratum local 
clock driver on the sever.

This is a good example of failing to specify the goal: 

More information about the questions mailing list