From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] i/o on a hangup channel asymmetry
Date: Sun, 19 Jul 2009 13:32:14 -0700 [thread overview]
Message-ID: <E9435F69-4E2E-44B6-8FA0-4B03C0E4E0D2@sun.com> (raw)
In-Reply-To: <cb9353c73dbc7bf00968d179b5f51372@terzarima.net>
On Jul 19, 2009, at 2:30 AM, Charles Forsyth wrote:
>> perhaps i've been asleep at the swtch, but i don't recall seing
>> writes
>> on closed channels terminate programs with a note.
>
> sys: write on closed pipe
>
> mainly to kill off a pipeline when the thing at the end has finished.
> i think that might be the only instance where a note is used.
I had considered this theory. And it definitely explains why such
a behavior would be beneficial for the pipelined jobs. What
makes me unhappy, though, is that for things that are *not*
connected to the pipe, but rather to a different kind of channel,
it makes things more difficult without any clear benefit.
Even for the pipelined case -- consider what happens when the
thing at the beginning exits: the next consumer has to be aware
of EOF condition first (and if it skips over EOF of the read returning
-1). The consumers are offered a chance to shutting down
gracefully, where the producers are not.
Why inequality?
Thanks,
Roman.
next prev parent reply other threads:[~2009-07-19 20:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 18:39 Roman V. Shaposhnik
2009-07-19 1:06 ` erik quanstrom
2009-07-19 9:30 ` Charles Forsyth
2009-07-19 20:32 ` Roman Shaposhnik [this message]
2009-07-19 21:01 ` Francisco J Ballesteros
2009-07-20 4:49 ` Roman Shaposhnik
2009-07-20 9:53 ` Charles Forsyth
2009-07-20 17:01 ` Roman V Shaposhnik
2009-07-20 18:38 ` Charles Forsyth
2009-07-19 21:11 ` Mechiel Lukkien
2009-07-19 21:55 ` Charles Forsyth
2009-07-20 4:52 ` Roman Shaposhnik
2009-07-20 5:21 ` erik quanstrom
2009-07-20 16:53 ` Roman V Shaposhnik
2009-07-21 1:01 ` erik quanstrom
2009-07-21 2:04 ` Russ Cox
2009-07-21 2:15 ` erik quanstrom
2009-07-23 12:15 ` roger peppe
2009-07-20 9:52 ` Charles Forsyth
2009-07-20 17:14 ` Roman V Shaposhnik
2009-07-19 20:06 ` Roman Shaposhnik
2009-07-19 20:22 ` erik quanstrom
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=E9435F69-4E2E-44B6-8FA0-4B03C0E4E0D2@sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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).