From: Alex Riesen <alexander.riesen@synopsys.COM>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EINTR
Date: Mon, 30 Dec 2002 11:52:15 +0100 [thread overview]
Message-ID: <20021230105215.GA26221@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <007301c2aeca$193892c0$3640a8c0@boemboem>
Folkert van Heusden, Sun, Dec 29, 2002 00:37:34 +0100:
> Hi,
>
> I always thought: you should always check for errno==EINTR when doing
> read/write/recv/recvfrom/sendto.
> But today I heard that when using Linux, EINTR does NEVER occur when
> doing read/etc. on files.
> Is this true?
It was definitely true for 2.4.9.
Even on NFS mounted files.
What happen if the volumes mounted with intr, btw?
> And also: is this also true for sockets? and recv & friends?
No. You _have_to_ check EINTR for sockets, fifos, and pipes.
-alex
prev parent reply other threads:[~2002-12-30 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 23:37 EINTR Folkert van Heusden
2002-12-30 10:52 ` Alex Riesen [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=20021230105215.GA26221@riesen-pc.gr05.synopsys.com \
--to=alexander.riesen@synopsys.com \
--cc=folkert@vanheusden.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®