On Sat, Aug 22, 2020 at 03:51:48PM +0200, Otto Moerbeek wrote:
> Hi,
>
> At the moment ntpd never goes into unsynced mode if network
> connectivity is lost. The code to do that is only triggered when a
> pakcet is received, which does not happen.
>
> This diff fixes that by going into unsynced
On Tue, Aug 25, 2020 at 07:05:31PM +0200, Matthias Schmidt wrote:
> Hi Otto,
>
> * Otto Moerbeek wrote:
> > Hi,
> >
> > At the moment ntpd never goes into unsynced mode if network
> > connectivity is lost. The code to do that is only triggered when a
> > pakcet is received, which does not happen
Hi Otto,
* Otto Moerbeek wrote:
> Hi,
>
> At the moment ntpd never goes into unsynced mode if network
> connectivity is lost. The code to do that is only triggered when a
> pakcet is received, which does not happen.
>
> This diff fixes that by going into unsynced mode if no time data was
> proc
Hi,
At the moment ntpd never goes into unsynced mode if network
connectivity is lost. The code to do that is only triggered when a
pakcet is received, which does not happen.
This diff fixes that by going into unsynced mode if no time data was
processed for a while.
An earlier version of this d
