From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pipefile with regular file
Date: Tue, 1 Aug 2000 22:29:50 -0400 [thread overview]
Message-ID: <200008020230.WAA11041@cse.psu.edu> (raw)
> But I am having a problem with reads on a filtered regular file not ever
> hitting EOF:
The kernel has a ref on the other end of the pipe because it's still
available to be opened and used again. You'll never see EOF.
There were a couple of missing calls to close in the code I sent, but
even if you close everything in sight, you'll never see EOF. There's a
twisty maze of circular dependencies holding the structure up.
As I said in the beginning, this trick is suitable for continuous
files such as devices, but not for regular files.
-rob
next reply other threads:[~2000-08-02 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 2:29 rob pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-01 14:30 Stephen Harris
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=200008020230.WAA11041@cse.psu.edu \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).