On Sun, Feb 1, 2015 at 11:19 AM, Guus Sliepen <[email protected]> wrote: > On Sun, Feb 01, 2015 at 04:08:47PM +0900, crocket wrote: > >> If tincd is started before name resolution comes up, it keeps failing >> for ever to resolve domain names in Address= host configuration >> variable after name resolution becomes possible. >> >> I think tincd should succeed in resolving domain names after name >> resolution becomes available. > > The problem is when /etc/resolv.conf is changed while a program is > running, glibc doesn't automatically notice this. Since tinc 1.0.25 and > 1.1pre11, if you send tincd the ALRM signal, it will force glibc to > reload /etc/resolv.conf.
Considering how cheap that operation seems to be, would it make sense to call res_init() every time tinc retries a metaconnection? It's not doing that very often anyway... and it would solve the OP's problem. _______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
