Thanks for the info, I figured it was something like this going on. I may
try refining things to a different server if necessary.
My Ubuntu-Mate desktop time always seems synced, but sudo systemctl status
systemd-timesyncd gives:
systemd-timesyncd.service - Network Time Synchronization
>
> For wku...
pool.ntp.org is not a server.
It is a front end service for a pool of ntp servers, that can be anywhere
in the world.
There are hundreds, if not thousands of them in the pool.
To level the loading on the ntp servers within the pool, you will get
assigned to a different server
Well, I loaded Debian 8.2 on one of my BBB's, and then did a cold start and
you
can see the following in syslog. timesyncd starts off at a 32 second sntp
resync with the server, then moves up in powers of two to a maximum sync
time of about 34 minutes.
You can see it is making only single digit
On Saturday, December 9, 2017 at 1:16:51 PM UTC-6, William Hermans wrote:
>
>
> If you're serious about keeping time. Then get an accurate real time
> clock, and sync your system clock off that. Then update the real time clock
> once every month, or however often you need in order to keep time
On Sat, Dec 9, 2017 at 12:08 PM, wrote:
> Thanks, glad to see I'm not the only one with the issue. Did some more
> searching and it seems it only logs the sync that happens at daemon start
> up, but is supposed to resync at some compiled in interval. Check the most
> recent
Thanks, glad to see I'm not the only one with the issue. Did some more
searching and it seems it only logs the sync that happens at daemon start
up, but is supposed to resync at some compiled in interval. Check the most
recent sync time with the times from stat /var/lib/systemd/clock
On my
I have been chasing something similar.
On Debian 8.8 and prior Jessie versions, systemd-timesyncd worked very well
and issued a lot of (level debug) messages that told you what was going on,
and the level of correction being applied.
When it is running the time would stay synced within 20