>>> > Another question I have is about the NTP status output of timedatectl.
>>> >
>>> > Right now (with ntpd running) it says:
>>> >
>>> > NTP enabled: yes
>>> > NTP synchronized: no
>>> >
>>> > I suppose it need some more uptime than the 11 minutes I have
>>> > currently?
>>>
>>> Possibly, ntpd
On Tue, Aug 26, 2014 at 3:37 AM, Lennart Poettering
wrote:
> On Fri, 22.08.14 10:13, Miroslav Lichvar (mlich...@redhat.com) wrote:
>
>> > Polluting my log this way. Is is possible to inhibit that behavior? Maybe
>> > trying a couple of times, then giving up until next network status change.
>>
>>
On Fri, 22.08.14 10:13, Miroslav Lichvar (mlich...@redhat.com) wrote:
> > Polluting my log this way. Is is possible to inhibit that behavior? Maybe
> > trying a couple of times, then giving up until next network status change.
>
> Hm, a well behaved client reduces its polling rate exponentially
On Thu, Aug 21, 2014 at 08:15:36PM +0200, Florian Lindner wrote:
> Aug 21 09:45:00 asaru systemd-timesyncd[317]: Timed out waiting for reply
> from 216.239.32.15:123 (time1.google.com).
> Aug 21 09:45:00 asaru systemd-timesyncd[317]: Using NTP server
> [2001:4860:4802:32::f]:123 (time1.google.com
Hello,
I tried out timesyncd today. Basically worked out of the box (disabled ntpd,
enabling systemd-timesyncd and systemd-networkd, both unconfigured, side by
side with NetworkManager).
At my universities network they are blocking outgoing UDP why I can't reach
any NTP timesyncd gives these m
