On 17 August 2017 at 09:13, Karl Palsson <ka...@tweak.net.au> wrote: > > Hans Dedecker <dedec...@gmail.com> wrote: >> On Thu, Aug 17, 2017 at 1:25 PM, Karl Palsson >> <ka...@tweak.net.au> wrote: >> > >> > Ok, so this was broken after busybox 1.23.2 and not fixed until >> > 1.27 via >> > >> > https://git.busybox.net/busybox/commit/networking/ntpd.c?id=b62ea34afed7d3bf60a6c8ef5a030fea52f55b10 >> > >> > Presumably updating busybox in master isn't exactly on the >> > roadmap. Would a backport of this patch be acceptable for both >> > 17.01 and master? >> I'm in favor to backport the patch to 17.01; for master there's >> a pending patch to upstep to busybox 1.27 >> (https://patchwork.ozlabs.org/patch/801034/) > > > I've actually been testing the backport of the patch to ntpd > alone, and while it appears to do the right thing, it still never > actually syncs. (See below) > > Hans: does your 1.27 update actually work? (there's a bunch of > other changes in 1.27, I only backported the ntpd patch) > > Nathanial: Is this what's _meant_ be happening after your patch? > It certainly _looks_ better, but isn't actually syncing... > > Sincerely, > Karl Palsson
I discovered this issue a long time ago but my devices sync fine after putting somewhere.working.org as the first device. _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
