--
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 beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks William. I will see how I get on with the default systemd service that comes with the BBB Debian 8.2 image. If I continue to struggle obtaining an accurate time when polling the UK servers with systemd then I will likely change to another NTP service.I will keep this post update with my findings.
--
Robert Nelson, what did you do for updating time on the latest Wheezy images. Starting around 7.8 I guess. They seemed to work mostly seamlessly, without slowing down the boot process too much. rc.d ?
With wheezy it was just ntpdate... It's biggest issue, it doesn't know when the network is up.. So if you look in the log, you'll see it try and give up on bootup.. Usually have to call it manually... While systemd-timesyncd handles that situation.
--
It looks like the time is actually correct since I update the time servers. I was comparing it to the clock on my Windows 10 PC which appears to be 5 seconds too slow! This clock, if accurate, is matching the time on my BBB, http://www.timeanddate.com/worldclock/uk/london
Never trust windows time, you can do really funny things on a windows network. At work, they use to purposely set our laptop clocks back 5mins.. Along with disabling our ability to change the time dns server thru the normal admin panel.. a few reg hacks later we had it fixed..
--