/etc/resolv.conf seems to be read only on client's startup.
Thus when changing IP or network, already running clients never know the content of any update in /etc/resolv.conf. This is very annoying on computers such as laptop which can fetch new network information through DHCP.
Here is patch that seems to do the trick for this situation.
Patch is from <URL:http://sources.redhat.com/ml/libc-alpha/2004-09/msg00130.html> with a few modifications to apply properly with glibc-2.4.
Feel free to add these modifications in the list of patches.
Created attachment 98071 [details, diff]
Force reload of /etc/resolv.conf whenever it is updated
Patch is small and really simple to read and to see what it does. Feel free to modify it.
doesnt this address what you want to do ?
(In reply to comment #2)
> doesnt this address what you want to do ?
More or less. I already tried this but it did not work.
All I know is that either Debian and Ubuntu commited a patch like the one I am submitting.
Actually, this is the solely way I have found working for me.
point being that the patch/idea was proposed on the glibc mailing list and it was completely shot down
i'm not too keen on maintaining things where upstream flat out said no ... but that doesnt mean we will
Up to you guys :)
I opened a bug report since another people has the same problem. I recommended, as upstream does, to use nscd instead.
This is not vital to use or not the patch. What I want, is an elegant way to ack clients on resolv.conf update. If there is a clearer solution, I am likely to use it instead of this hack.
Oh, by the way, why did the patch get "shot down" ? It works.
upstream said to use nscd
Ok then you can close this bug report since nothing will be done.