* EINTR
@ 2002-12-28 23:37 Folkert van Heusden
2002-12-30 10:52 ` EINTR Alex Riesen
0 siblings, 1 reply; 2+ messages in thread
From: Folkert van Heusden @ 2002-12-28 23:37 UTC (permalink / raw)
To: linux-kernel
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?
And also: is this also true for sockets? and recv & friends?
Folkert van Heusden
www.vanheusden.com/Linux
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: EINTR
2002-12-28 23:37 EINTR Folkert van Heusden
@ 2002-12-30 10:52 ` Alex Riesen
0 siblings, 0 replies; 2+ messages in thread
From: Alex Riesen @ 2002-12-30 10:52 UTC (permalink / raw)
To: Folkert van Heusden; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-12-30 10:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-12-28 23:37 EINTR Folkert van Heusden
2002-12-30 10:52 ` EINTR Alex Riesen
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®