| To: | "Bernard MAUDRY" <support@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: PROBLEM: a local TCP socket close does not trigger a poll on the other end |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Sat, 3 Mar 2001 02:52:24 -0800 (PST) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <3AA0DA38.23766.573498DB@localhost> |
| References: | <3AA0DA38.23766.573498DB@localhost> |
| Sender: | owner-netdev@xxxxxxxxxxx |
Set the FDs[0].events to some value other than zero, you are telling the kernel you are interested in "no events". Read the poll() man page for details. Later, David S. Miller davem@xxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | PROBLEM: a local TCP socket close does not trigger a poll on the other end, Bernard MAUDRY |
|---|---|
| Next by Date: | IPv6: if sitX used, and take eth down, infinite errors, Pekka Savola |
| Previous by Thread: | 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] |