From: Andi Kleen <ak@suse.de>
To: Manfred Bartz <mbartz@optushome.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: connect() does not return ETIMEDOUT
Date: 13 Aug 2001 18:15:06 +0200 [thread overview]
Message-ID: <ouplmkogcmt.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <20010813140049.28744.qmail@optushome.com.au.suse.lists.linux.kernel>
In-Reply-To: Manfred Bartz's message of "13 Aug 2001 16:03:57 +0200"
Manfred Bartz <mbartz@optushome.com.au> writes:
> When a TCP client opens multiple connections beyond the server's
> backlog capacity, the call to connect() returns a value of zero
> (success) after 9 seconds. Toggling SYN-cookies makes no difference.
It works correct here (2.4.7-something)
# ipchains -A input -j DENY -p tcp --dport 10000
# strace -e connect telnet localhost 10000
...
connect(3, {sin_family=AF_INET, sin_port=htons(10000), sin_addr=inet_addr("127.0.0.1")}}, 16) = -1 ETIMEDOUT (Connection timed out)
If you think something is wrong you should probably send a strace that
shows it.
-Andi
next parent reply other threads:[~2001-08-13 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010813140049.28744.qmail@optushome.com.au.suse.lists.linux.kernel>
2001-08-13 16:15 ` Andi Kleen [this message]
2001-08-15 14:34 ` connect() does not return ETIMEDOUT Manfred Bartz
2001-08-17 13:11 Alessandro Motter Ren
2001-08-17 22:39 ` Alexey Kuznetsov
[not found] <Pine.LNX.4.21.0108151123510.4809-100000@w-sridhar2.des.sequent.com.suse.lists.linux.kernel>
[not found] ` <20010816005902.16224.qmail@optushome.com.au.suse.lists.linux.kernel>
2001-08-16 1:39 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 21:41 Sridhar Samudrala
2001-08-16 0:59 ` Manfred Bartz
2001-08-13 14:00 Manfred Bartz
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=ouplmkogcmt.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbartz@optushome.com.au \
/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