From: bert hubert <ahu@ds9a.nl>
To: Michael T Kerrisk <mtk-lists@gmx.net>
Cc: netdev@oss.sgi.com
Subject: Re: SO_REUSEADDR behavior different from BSD
Date: Thu, 5 Aug 2004 16:14:44 +0200 [thread overview]
Message-ID: <20040805141444.GA2292@outpost.ds9a.nl> (raw)
In-Reply-To: <16224.1091629527@www2.gmx.net>
On Wed, Aug 04, 2004 at 04:25:27PM +0200, Michael T Kerrisk wrote:
> But on Linux (2.6), the bind() fails with EADDRINUSE.
This scenario has previously worked for me. Can you show the exact source
which exhibits this problem?
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-08-05 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 14:25 SO_REUSEADDR behavior different from BSD Michael T Kerrisk
2004-08-05 14:14 ` bert hubert [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 22:25 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=20040805141444.GA2292@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=mtk-lists@gmx.net \
--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).