From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rx - wot no stderr?
Date: Fri, 19 Jan 2007 20:34:56 -0500 [thread overview]
Message-ID: <6efdb74d50a095dd019ef975607c19d4@coraid.com> (raw)
In-Reply-To: <df3ead9fb0547531720b87f46821951f@quintile.net>
On Fri Jan 19 20:17:18 EST 2007, steve@quintile.net wrote:
> > if you are talking to a plan 9 server, stderr already works:
>
> I don'r believe it does in the way I mean. The server-side of cpu opens
> /mnt/term/dec/cons for stdout and again for stderr so you cannot run a remote
> program, and locally redirect its stdout and stderr (without using a
> temporary file in a shared file space for one or t'other as already mentioned.
>
you're right. my example is flawed. here's a better illustration of what's going
on:
cpu% cpu -c echo fu '>[1=2]' ';' echo bar >[2=]
fu
bar
- erik
next prev parent reply other threads:[~2007-01-20 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 17:14 Steve Simon
2007-01-19 12:32 ` Gorka guardiola
2007-01-19 13:07 ` erik quanstrom
2007-01-19 14:35 ` Steve Simon
2007-01-19 22:17 ` erik quanstrom
2007-01-20 1:15 ` Steve Simon
2007-01-20 1:34 ` erik quanstrom [this message]
2007-01-24 21:03 ` rog
2007-01-21 7:06 ` ron minnich
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=6efdb74d50a095dd019ef975607c19d4@coraid.com \
--to=quanstro@coraid.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).