| To: | mtk-lists@xxxxxxx |
|---|---|
| Subject: | Re: SO_REUSEADDR behavior different from BSD |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxx> |
| Date: | Thu, 05 Aug 2004 11:34:37 -0700 (PDT) |
| Cc: | ahu@xxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <19686.1091723777@xxxxxxxxxxxxx> |
| References: | <20040805141444.GA2292@xxxxxxxxxxxxxxx> <19686.1091723777@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
In article <19686.1091723777@xxxxxxxxxxxxx> (at Thu, 5 Aug 2004 18:36:17 +0200 (MEST)), "Michael T Kerrisk" <mtk-lists@xxxxxxx> says: > Now, on Linux, at this point, the second instance of the > server fails with EADDRINUSE, even though it did use > SO_REUSEADDR. On FreeBSD 5.1, the second server instance > does successfully bind. This behavior is intended. First socket is REQUIRED to set SO_REUSEADDR I hate BSD's behavior because it is asynmetry. (Both sockets are required to agree on "REUSEADDR.") -- Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@xxxxxxxxxxxxxx> GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: SO_REUSEADDR behavior different from BSD, David Stevens |
|---|---|
| Next by Date: | Re: [IPSEC] add missing flow_cache_genid update to xfrm_policy_delete(), Herbert Xu |
| Previous by Thread: | Re: SO_REUSEADDR behavior different from BSD, David Stevens |
| Next by Thread: | Re: SO_REUSEADDR behavior different from BSD, Fernando Gont |
| Indexes: | [Date] [Thread] [Top] [All Lists] |