[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: busybox 1.25 ntpd retry initial DNS resolution (forever, no timeout for now).
From:       Natanael Copa <ncopa () alpinelinux ! org>
Date:       2016-06-29 11:03:50
Message-ID: 20160629130350.4e915968 () ncopa-desktop ! copa ! dup ! pw
[Download RAW message or body]

On Tue, 28 Jun 2016 20:19:29 +0200
"KP.Kirchdoerfer" <kapeka@bering-uclibc.de> wrote:

> Hi;
> 
> I'm testing busybox 1.25 and wonder how to deal with the commit 
> 
> https://git.busybox.net/busybox/commit/networking?id=e4caf1dd9ce8569371a0eeb77ccf02a572dc0f11
> 
> At the first look it seems to be an obvious improvement, but then I'm afraid it 
> may generate a hard to resolve problem.
> 
> I start ntpd by default from /etc/init.d
> 
> There might be no working network connection (not configured properly for 
> whatever reason, hardware problems, whatelse).
> 
> With busybox 1.24 ntpd fails to start and the boot process continues up to a 
> shell login  - allowing me to configure, start diagnostics and resolve errors.
> 
> With busybox 1.25 ntpd seems to loop forever if now NTP servers are found, 
> blocking the boot process  and I never get a login to solve a possible pb or 
> to do a first time configuration.
> 
> Any hints how this can be solved?

It looks like the original implementation from Kaarle[1] handled it better.

Also, if you add multiple ntp servers and the first is broken, then
will ntpd never set time. Kaarle's implementation would just skip the
bad server and use the working. To test:

  ./busybox ntpd -d -n -p qwe.rty.ghj.kl -p 0.no.pool.ntp.org


And finally, bloat check on x86_64 suggests that Kaarles implementation
is -41 bytes compared to current git master.



[1]: http://lists.busybox.net/pipermail/busybox/2016-May/084197.html

-nc
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic