| To: | support@xxxxxxxxxxxxx (Bernard MAUDRY) |
|---|---|
| Subject: | Re: PROBLEM: a local TCP socket close does not trigger a poll on the other end |
| From: | kuznet@xxxxxxxxxxxxx |
| Date: | Sun, 11 Mar 2001 20:52:34 +0300 (MSK) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <3AA7D0B4.8123.10893F11@localhost> from "Bernard MAUDRY" at Mar 10, 1 04:45:01 pm |
| Sender: | owner-netdev@xxxxxxxxxxx |
Hello! > So putting 0 in the events fields is a normal value when the application is > only > insterested in the error cases. Absolutely right! If poll returns, it will return you all the events. But it will not return until an unmaskable condition will happen. In your case it will never return. > hangup of the other end. There is no hangup. You may write to this socket. Alexey |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: weird implementation of ipip and sit tunnels, kuznet |
|---|---|
| Next by Date: | Re: [Fwd: Re: possible bug x86 2.4.2 SMP in IP receive stack], kuznet |
| Previous by Thread: | Re: PROBLEM: a local TCP socket close does not trigger a poll on the other end, Bernard MAUDRY |
| Next by Thread: | Re: PROBLEM: a local TCP socket close does not trigger a poll on the other end, Bernard MAUDRY |
| Indexes: | [Date] [Thread] [Top] [All Lists] |