From: Andi Kleen <ak@suse.de>
To: Adam Scislowicz <adams@fourelle.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Non-Blocking socket (SOCK_STREAM send)
Date: Fri, 15 Dec 2000 00:35:33 +0100 [thread overview]
Message-ID: <20001215003533.A26106@gruyere.muc.suse.de> (raw)
In-Reply-To: <3A3953DB.CDA2DF4E@fourelle.com> <20001215002032.A24018@gruyere.muc.suse.de> <3A39573D.BB731C8@fourelle.com>
In-Reply-To: <3A39573D.BB731C8@fourelle.com>; from adams@fourelle.com on Thu, Dec 14, 2000 at 03:26:53PM -0800
On Thu, Dec 14, 2000 at 03:26:53PM -0800, Adam Scislowicz wrote:
> We understand the meaning of EPIPE, the question is why 2.4.x is returning EPIPE,
> while 2.2.x is succeeding in sending
> the data to thttpd. Using the 2.2.x kernel our proxy functions, and I can access
> thttpd directly. In 2.4.x I can access thttpd
>From your subject you seem not to.
To the best of my knowledge the receiver side EPIPE reporting has not changed,
so it must be something in the sender that causes it to close the connection
earlier. What you have to find out.
> I have already noticed that the 2.4.x kernel does not set errno = 0 in many places
> where the 2.2.x kernel did, so there are
> differences.
No system call ever sets errno = 0.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-15 0:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 23:12 Adam Scislowicz
2000-12-14 23:20 ` Andi Kleen
2000-12-14 23:26 ` Adam Scislowicz
2000-12-14 23:35 ` Andi Kleen [this message]
2000-12-14 23:54 ` Adam Scislowicz
2000-12-15 0:03 ` Andi Kleen
2000-12-15 22:10 ` Non-Blocking socket (SOCK_STREAM send) - SOLVED Adam Scislowicz
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=20001215003533.A26106@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=adams@fourelle.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®