netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael T Kerrisk" <mtk-lists@gmx.net>
To: YOSHIFUJI.Hideaki/^[$B5HF#1QL@^[.sgi.com (B <yoshfuji@wide.ad.jp>)
Cc: ahu@ds9a.nl, netdev@oss.sgi.com, David Stevens <dlstevens@us.ibm.com>
Subject: Re: SO_REUSEADDR behavior different from BSD
Date: Fri, 6 Aug 2004 00:25:19 +0200 (MEST)	[thread overview]
Message-ID: <20734.1091744719@www51.gmx.net> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 911 bytes --]

> In article <19686.1091723777@www48.gmx.net> (at Thu, 5 Aug 2004 18:36:17
> +0200 (MEST)), "Michael T Kerrisk" <mtk-lists@gmx.net> 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, David,

Thank you for the information / confirmation that this is intended
behavior.  I'll try to see that something on this point makes it 
into the man pages.

Cheers,

Michael

-- 
Michael Kerrisk
mtk-lists@gmx.net

NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl

             reply	other threads:[~2004-08-05 22:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 22:25 Michael T Kerrisk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-04 14:25 SO_REUSEADDR behavior different from BSD Michael T Kerrisk
2004-08-05 14:14 ` bert hubert
2004-08-05 16:36   ` Michael T Kerrisk
2004-08-05 18:20     ` David Stevens
2004-08-05 18:34     ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-08  2:25       ` Fernando Gont
2004-08-09 13:29         ` Michael T Kerrisk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20734.1091744719@www51.gmx.net \
    --to=mtk-lists@gmx.net \
    --cc=ahu@ds9a.nl \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).