Re: [musl] nslookup failures with coarse CLOCK_MONOTONIC

2022-10-07 Thread Rich Felker
On Sat, Oct 08, 2022 at 01:53:29AM +0200, Jo-Philipp Wich wrote: > Hi, > > > [...] > > Which implementation of nslookup is this? Busybox? It would probably > > be useful to hear thoughts on it from their side. > assuming the OP is using standard OpenWrt nslookup, it is the "big" busybox >

Re: [musl] nslookup failures with coarse CLOCK_MONOTONIC

2022-10-07 Thread Jo-Philipp Wich
Hi, > [...] > Which implementation of nslookup is this? Busybox? It would probably > be useful to hear thoughts on it from their side. assuming the OP is using standard OpenWrt nslookup, it is the "big" busybox nslookup implementation, which is using the res_*() api and name lookup logic borrowed

Re: [musl] nslookup failures with coarse CLOCK_MONOTONIC

2022-10-07 Thread Rich Felker
On Sat, Oct 08, 2022 at 01:04:25AM +0200, Uwe Kleine-König wrote: > Hello, > > on a TP-Link RE200 v1 (platform = ramips/mt7620) I experience often: > > root@ares:~# nslookup www.openwrt.org > Server: 127.0.0.1 > Address: 127.0.0.1:53 > > Non-authoritative answer: >