From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: Ken Brown <kbrown@cornell.edu>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [EXTERNAL] Re: FIFO issues
Date: Tue, 20 Sep 2022 03:51:29 +0000 [thread overview]
Message-ID: <SJ0PR09MB710202DE2D8B5F4FEDCBD482A54C9@SJ0PR09MB7102.namprd09.prod.outlook.com> (raw)
In-Reply-To: <9e531437-9e27-969f-517e-ec5607212c76@cornell.edu>
> It seems that there's an exception: If no process has ever had the FIFO open for
> writing since it was opened for reading, then the FIFO is not considered to be
> at end-of-file.
IMO, when a virgin FIFO is read with a blocking read (of just one byte), it will block -- it will not return 0.
Meaning that such a FIFO was not ready for read (when the other end was not (yet) attached / written), and
also meaning that there was no EOF (which is obvious because a transaction has not even started).
select() should indicate just the same (and it does so on the discussed platforms) regardless of O_NONBLOCK.
Anton Lavrentiev
Contractor NIH/NLM/NCBI
next prev parent reply other threads:[~2022-09-20 3:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 21:45 Enrico Forestieri
2022-09-19 19:15 ` Ken Brown
2022-09-19 19:50 ` Norton Allen
2022-09-19 19:53 ` Norton Allen
2022-09-19 21:25 ` Ken Brown
2022-09-19 21:28 ` Norton Allen
2022-09-19 22:05 ` Enrico Forestieri
2022-09-19 23:54 ` Ken Brown
2022-09-20 3:51 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2022-09-20 6:54 ` Enrico Forestieri
2022-09-20 13:18 ` Ken Brown
2022-09-20 17:20 ` Enrico Forestieri
2022-09-23 15:36 ` Ken Brown
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=SJ0PR09MB710202DE2D8B5F4FEDCBD482A54C9@SJ0PR09MB7102.namprd09.prod.outlook.com \
--to=lavr@ncbi.nlm.nih.gov \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).