From: "Saurabh Sehgal" <saurabh.r.s@gmail.com>
To: Steve Graegert <graegerts@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: EAGAIN with read
Date: Thu, 6 Dec 2007 18:27:32 -0500 [thread overview]
Message-ID: <2a46ebd60712061527r42b53cc3i444811873ebba7d7@mail.gmail.com> (raw)
In-Reply-To: <6a00c8d50712061329oc49de6fpdff81748bbfbe57b@mail.gmail.com>
Hi,
Thanks for the reply .. right now, i was reading and checking for the
errno EAGAIN, but my loop would prematurely exit. I later found out
that the errnor returned by read was ECHILD ... looking at the read(3)
manpages ... this errno is not mentioned
But since the process that is supposed to write to the pipe is a
forked processs .. does that change anything ?
Thanks,
Saurabh
On Dec 6, 2007 4:29 PM, Steve Graegert <graegerts@gmail.com> wrote:
>
> On Dec 6, 2007 9:14 PM, Saurabh Sehgal <saurabh.r.s@gmail.com> wrote:
> > Hi,
> >
> > I had a basic question about read . I have a file descriptor marked
> > with non blocking I/O , and I want to read data from the file
> > descriptor. This file descriptor is the read end of a UNIX pipe.
> >
> > The process that the pipe reads from is a very slow process. Hence I
> > need to poll and keep on trying to read from the fd until the process
> > has actually written something to the pipe. I execute read while the
> > errno condition EAGAIN is true. Will this ever result in an infinite
> > loop ? (lets say the remote process dies and doesnt write anything to
> > the pipe, will I go into an infinite loop since I am polling while
> > EAGAIN is true ?).
>
> Hi,
>
> I'd suggest taking a look at select(2) which allows for the
> specification of a timeout. Use pselect(2) if you are waiting for a
> signal as well as data from a file descriptor or otherwise the
> select(2) call may block indefinitely due to a nasty race condition
> that may occur.
>
> To your question: There are actually a couple of reasons why your
> process would or would not run indefinitely in that loop. There are
> also a couple of other errors read(3) can return that might cause your
> condition to return false, thus breaking the loop (if I understood
> correctly, code example is welcome). What about EINTR which is
> returned when the call was interrupted by a signal before any data was
> read? (Please note that for a FIFO or pipe it will never return EINTR
> if any data has been read.)
>
> \Steve
>
> --
>
> Steve Grägert
> DigitalEther.de
>
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-12-06 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 20:14 EAGAIN with read Saurabh Sehgal
2007-12-06 21:29 ` Steve Graegert
2007-12-06 23:27 ` Saurabh Sehgal [this message]
2007-12-08 19:12 ` Steve Graegert
2007-12-10 16:21 ` Saurabh Sehgal
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=2a46ebd60712061527r42b53cc3i444811873ebba7d7@mail.gmail.com \
--to=saurabh.r.s@gmail.com \
--cc=graegerts@gmail.com \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).