Subject: Re: re-reading /etc/resolv.conf on change
To: Manuel Bouyer <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 01/06/2004 14:45:34
[ On Tuesday, January 6, 2004 at 20:27:05 (+0100), Manuel Bouyer wrote: ]
> Subject: Re: re-reading /etc/resolv.conf on change
> No, the changes should be picked up immediatly, otherwise you may end
> up waiting for nameserver timeouts, which isn't good.
One waits for nameserver timeouts often enough regardless -- i.e. I
don't think this is an issue from a human factors point of view.
Of course comparing stat( _PATH_RESCONF) values at appropriate intervals
is still the best approach. :-)
If and when ISC choose to decide to add something like res_getconfname()
(and res_setconfname()) then they can be used in lieu of the hard-coded
pathname that res_init() itself now uses and all will remain "compatible".
Greg A. Woods
+1 416 218-0098 VE3TCP RoboHack <firstname.lastname@example.org>
Planix, Inc. <email@example.com> Secrets of the Weird <firstname.lastname@example.org>