resolv for instance cycles through its listed servers, so if your first
server is down, it will switch to the next after a time out. *But* this
time out will be suffered for all applications over and over.
Here, it should be possible to record the failure somewhere after the first
timeout, so that subsequent uses of the resolv library will immediately
switch to the second server.
Of course, it's possible to hack something up for resolv (just like Netscape
does it for its proxies), but it seems that it should be possible to come up
with a more generic solution that would `fix' each and every such application
once and for all.
Stefan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/