From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] Subject:unpipeIt'seasy for a process to insert a new process intoapipelineeither upstream or down unpipe
Date: Wed, 09 Jul 2014 22:49:22 -0400 [thread overview]
Message-ID: <201407100249.s6A2nMh3017869@coolidge.cs.dartmouth.edu> (raw)
It's easy for a process to insert a new process into a
pipeline either upstrean or downstream. Was there ever a
flavor of Unix in which a process could excise itselfa
from a pipeline without breaking the pipeline?
Doug
next reply other threads:[~2014-07-10 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 2:49 Doug McIlroy [this message]
2014-07-10 4:52 ` [TUHS] Excise process from a pipe Warren Toomey
2014-07-10 5:00 ` Dave Horsfall
2014-07-10 5:06 ` Christopher Vance
2014-07-10 8:43 ` Warren Toomey
2014-07-10 12:03 ` Doug McIlroy
2014-07-10 12:04 ` Doug McIlroy
2014-07-10 14:45 ` Larry McVoy
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=201407100249.s6A2nMh3017869@coolidge.cs.dartmouth.edu \
--to=doug@cs.dartmouth.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).