Messages in this thread | | | From | Stefan Monnier <monnier+lists/linux/kernel/news/@TEQUILA.SYSTEMSZ.CS.YALE.EDU> | Subject | Re: how to deal with hosts that are down | Date | 23 Sep 1998 16:56:52 -0400 |
| |
>>>>> "Brandon" == Brandon S Allbery KF8NH <allbery@kf8nh.apk.net> writes: > Sun beat you to it; it's called nscd. I understand there's a version for
No. I know about nscd, but it does just what I said I wasn't interested in: it solves the special case of DNS accesses (well maybe a few other services as well). What I have in mind is an OS-wide solution, so that if a host is down and someone tries to access it via resolv/ftp/telnet/http/younameit they will immediately get a timeout (since the host is know to be down because of an earlier timeout, why wait 2 minutes before returning the timeout to the application ?). I'm quite wawre that I haven't thought this out in detail and that it isn't quite so easy to solve, but I'm fairly sure something can be done.
Ideally, this should be coupled with a network-wide service (call it NSS for network-status-service) that would record what is up and what isn't. This is of course tricky business since the NSS server might go down :-(
This came to my mind when people mentionned the idea of keeping the tcp-window size from one connection to the next.
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/
| |