[email protected] said: > Thanks. The essential point (bind reacquisition failing after droproot) is > not NetBSD specific and is worth keeping in mind.
I think it works (on Fedora). My test case is closing the lid on a laptop, waiting a while, then opening it. 16 Apr 02:21:50 ntpd[636]: Deleting interface #4 wlp2s0b1, 192.168.1.100#123, interface stats: received=1189, sent=1259, dropped=0, active_time=10601 secs ... 16 Apr 02:21:50 ntpd[636]: Deleting interface #5 wlp2s0b1, fe80::864b:f5ff:fe39:244a%3#123, interface stats: received=0, sent=0, dropped=0, active_time=10601 secs 16 Apr 02:21:57 ntpd[636]: Listen normally on 6 wlp2s0b1 192.168.1.100:123 16 Apr 02:21:57 ntpd[636]: Listen normally on 7 wlp2s0b1 [fe80::864b:f5ff:fe39:244a%3]:123 16 Apr 02:21:57 ntpd[636]: new interface(s) found: waking up resolver 16 Apr 02:23:57 ntpd[636]: 74.120.8.2 132a 8a sys_peer 16 Apr 02:23:57 ntpd[636]: 0.0.0.0 0613 03 spike_detect -0.190987 s 16 Apr 02:24:14 ntpd[636]: 129.250.35.250 141a 8a sys_peer I think stock Fedora restarts ntpd in that case. I think I patched something to let it keep running, but I can't find any notes on what I did. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
