In previous OS releases, such as Debian 8.8, systemd-timesyncd was used as 
the 
network time synchronization.

It did an initial sync, then as it determined the time base correction 
necessary, corrected for the frequency error in the BBB's main clock, and 
kept 
increasing the time between network time syncs, until it was running/syncing
about once every thirty minutes.

You saw a bunch of line items in the syslogs that looked like the following

Dec  3 13:34:50 BBG4 systemd-timesyncd[209]: 
interval/delta/delay/jitter/drift 2048s/-0.001s/0.053s/0.011s/-72ppm
Dec  3 14:08:58 BBG4 systemd-timesyncd[209]: 
interval/delta/delay/jitter/drift 2048s/+0.002s/0.055s/0.012s/-71ppm


Now, in Debian 9.2, systemd-timesyncd is used for network time 
synchronization.

But in the syslogs, you only see a single report of time sync at the first 
boot, and nothing further.

Is systemd-timesyncd still doing a network sync every 30 minutes and just 
not 
logging it to syslog, or is it doing it less frequently?

If it is doing it less frequently, what is the easiest way to get back to 
the
30 minute re-sync cycle with the clock correction?

--- Graham

==

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7b79b9fa-12a1-4a0a-a157-5e356cdcb810%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to