Re: Our (real) problems
- From: Alan Cox <alan redhat com>
- To: danw ximian com (Dan Winship)
- Cc: mjs noisehavoc org (Maciej Stachowiak), michael ximian com (Michael Meeks), alexl redhat com (Alex Larsson), gnome-hackers gnome org, gnome-2-0-list gnome org
- Subject: Re: Our (real) problems
- Date: Tue, 4 Sep 2001 16:12:47 -0400 (EDT)
> Why, is the "broken" signal tied to X? Can't you get the same thing for
> non-X stuff by just pinging the other side of the connection every now
> and then? If you get an EPIPE, it's dead. The remote server doesn't even
> need to ack the ping.
The way this works with TCP is as follows. Reads from broken streams
generate an EOF, writes generate -1, EPIPE and a broken pipe signal
A broken tcp connect will generally be detected on a write (or up to 15 mins
after it if it takes time to time out the attempt) and if keepalives are
enabled "within about 2.5 hours anyway"
_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
