On Mon, Jun 27, 2016 at 5:34 AM, 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. > > This happens all too often with my deployments of Webconverger and I was > wondering if asking for HTTP based time synchronization was a sane thing > to ask for from systemd. > > An example implementation can be found here: > > https://github.com/ccrisan/motioneyeos/blob/master/board/common/overlay/etc/init.d/S50date#L31 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. (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 the respective ports or a local proxy in order to work. Timesyncd already supports picking up local NTP servers from DHCP, afaik.) -- Mantas Mikulėnas <graw...@gmail.com>
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
