From: Kurt Roeckx <Q@ping.be>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chris Evans <chris@scary.beasts.org>,
linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: Kernel bug with UNIX sockets not detecting other end gone?
Date: Fri, 18 May 2001 22:52:30 +0200 [thread overview]
Message-ID: <20010518225230.A19506@ping.be> (raw)
In-Reply-To: <20010518192422.B18162@ping.be> <E150qSZ-0007cw-00@the-village.bc.nu>
In-Reply-To: <E150qSZ-0007cw-00@the-village.bc.nu>
On Fri, May 18, 2001 at 09:02:51PM +0100, Alan Cox wrote:
> > What I'm seeing however in an other program is that select says I
> > can read from the socket, and that read returns 0, with errno set
> > to EGAIN. I call select() again, with returns and says I can read
>
> No no no. If the read does not return -1 it does not change errno. EOF isnt
> an error.
Of course, how stupid of me.
Kurt
prev parent reply other threads:[~2001-05-18 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 22:57 Kernel bug with UNIX sockets not detecting other end gone? Chris Evans
2001-05-17 22:59 ` Alan Cox
2001-05-17 23:51 ` Chris Evans
2001-05-18 0:32 ` David Schwartz
2001-05-18 8:32 ` Olaf Titz
2001-05-18 17:24 ` Kurt Roeckx
2001-05-18 20:02 ` Alan Cox
2001-05-18 20:52 ` Kurt Roeckx [this message]
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=20010518225230.A19506@ping.be \
--to=q@ping.be \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris@scary.beasts.org \
--cc=davem@redhat.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