On Mon, 27.06.16 10:34, Kai Hendry (hen...@webconverger.com) wrote:
> Hi there,
>
> I had a quick look at
> https://github.com/systemd/systemd/tree/master/src/timesync to try work
> out if /usr/lib/systemd/systemd-timesyncd had some sort of fallback if
> ntp UDP port 123 traffic is blocked.
>
>
Am 28.06.2016 um 05:20 schrieb Kai Hendry:
On Mon, 27 Jun 2016, at 08:33 PM, Reindl Harald wrote:
normally service level agreemnets contain basic prerequisites and if the
are ignored the customers has to pay a penalty in case of support cases
You live in a different world to me.
you are
On Mon, 27 Jun 2016, at 08:33 PM, Reindl Harald wrote:
> normally service level agreemnets contain basic prerequisites and if the
> are ignored the customers has to pay a penalty in case of support cases
You live in a different world to me.
Just going to follow up with a blog I found on the
Am 27.06.2016 um 08:30 schrieb Kai Hendry:
On Mon, 27 Jun 2016, at 01:03 PM, Mantas Mikulėnas wrote:
(I also have a strong dislike for network admins who cling to their "HTTP
only" firewall policies... I don't see why NTP is a 'lesser' protocol
than
HTTP and DNS, both of which require either
On Mon, 27 Jun 2016, at 01:03 PM, Mantas Mikulėnas wrote:
> Who would host the sync server? Or would you just point it at a random
> site
> and hope its operators don't mind? It's already bad enough that systemd
> defaults to Google's private NTP servers, IMHO.
Reminds me of the "Am I on the
On Mon, 27 Jun 2016, at 10:42 AM, Reindl Harald wrote:
> are you aware that in case of many machines you should setp *one* ntpd
> and the other machines only acess this internal host to take away load
> from pool.ntp.org which would also solve the problem access port 123
> outside your network
On Mon, Jun 27, 2016 at 5:34 AM, Kai Hendry wrote:
> Hi there,
>
> I had a quick look at
> https://github.com/systemd/systemd/tree/master/src/timesync to try work
> out if /usr/lib/systemd/systemd-timesyncd had some sort of fallback if
> ntp UDP port 123 traffic is
Hi there,
I had a quick look at
https://github.com/systemd/systemd/tree/master/src/timesync to try work
out if /usr/lib/systemd/systemd-timesyncd had some sort of fallback if
ntp UDP port 123 traffic is blocked.
This happens all too often with my deployments of Webconverger and I was
wondering
Am 27.06.2016 um 04:34 schrieb Kai Hendry:
I had a quick look at
https://github.com/systemd/systemd/tree/master/src/timesync to try work
out if /usr/lib/systemd/systemd-timesyncd had some sort of fallback if
ntp UDP port 123 traffic is blocked.
This happens all too often with my deployments of