On 31 Aug 2008, Giampaolo Tomassoni stated: >> How do you arrange that all the existing programs that have already >> sucked in resolv.conf note the change? They're generally not going to >> unless you restart them: nothing polls resolv.conf looking for changes >> to it as far as I know, that would be far too inefficient. > > Depending on the specific implementation of the resolver library, the > application may check for changes in the resolv.conf file. Maybe they don't > check at every and each resolv request, however: they may instead check for > changes every, say, 10 secs or maybe every 1.000 requests. This way, looking > for changes in the /etc/resolv.conf file is not that much inefficient...
Have you ever seen an implementation that does that? I haven't. glibc doesn't do it, unless I misread the code severely. Solaris doesn't do it. Does anything? -- `Not even vi uses vi key bindings for its command line.' --- PdS
