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. > > > > This diff fixes that by going into unsynced mode if no time data was > > processed for a while. > > > > An earlier version of this diff was tested by naddy@. Compared to that > > version, the needed period of inactivity is now three times as large > > and I set scale to 1, so recovery goes faster. > > > > Please test and review, > > I have your diff running on my Laptop which sometimes not connected to a > network so it should be a good test case. > > I haven't noticed any difference to before, so I count that as a good > sign :) I spotted only one thing: While "ntpctl -s a" says that the > clock is unsynced I see no message from ntpd in the logs. Not sure if > that's on purpose or not, I just noticed it.
Thanks for testing. There should be "clock is now unsynced" and "clock is now synced" messages in /var/log/daemon... here they do appear. -Otto