Previous email was a little premature, but more news on the subject: https://sourceware.org/bugzilla/show_bug.cgi?id=984
from what I can tell, MUSL reads the resolv.conf file on every call to __lookup_name()… so it shouldn’t have this issue. Then again, it’s a problem that’s more likely to afflict clients (especially roaming WiFi clients) being an LEDE router than LEDE itself. -Philip > On Jul 3, 2017, at 2:04 PM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: > > For everyone who has ever wondered why they need to stop and restart long > running services when they move from one network to another (as is common for > laptops using Wifi that are roaming around), this can be quite vexing. > > The reason was that /etc/resolv.conf would get rewritten by DHCP when you > acquired a new DHCP lease, but programs which were running wouldn’t have > sufficient knowledge to force the resolver to re-initialize itself (and > arguably, they shouldn’t have to… it should just work). > > This FINALLY (after many years) got fixed today: > > https://sourceware.org/bugzilla/show_bug.cgi?id=984 > > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=aef16cc8a4c670036d45590877d411a97f01e0cd > > So, hopefully that will make life easier for people who support their WiFi > users and will no longer have to say, “Have you tried stopping and restarting > the service?” > > https://www.youtube.com/watch?v=PtXtIivRRKQ > > Woot woot! > > -Philip _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
