Re: DNS caching(?) page-hangup issues and Opera 10.X

Kenneth Crudup <[email protected]> writes:

>> In the good news department, we believe we have found the problem with
>> name lookups when the network changes.  It seems glibc does not notice
>> changes to the DNS server addresses automatically.  But it seems it does
>> provide a function that can force it to reload the configuration.  There
>> is currently some discussion on how we can use it without breaking
>> anything.
>
> What about running "iwatch" on /etc/resolv.conf ? When that changes,
> reload the glibc DNS configuration.

I don't think we want to depend on iwatch being installed...

More importantly, the nasty part of the problem isn't detecting the
change, but in forcing the reload.  This part of the code is pretty ugly
and complex in order to work around various problems with the libc
resolver on various platforms.  So it isn't obvious that introducing
this change won't cause other problems.  (It is also not obvious exactly
what is required to make sure the configuration is properly reloaded.
Particularly across multiple platforms.)

eirik
--
Opera-Linux: https://list.opera.com/mailman/listinfo/opera-linux
More lists: https://list.opera.com/mailman/listinfo/
Unsubscribe: mailto:[email protected]?subject=unsubscribe