From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rx - wot no stderr?
Date: Sat, 20 Jan 2007 01:15:06 +0000 [thread overview]
Message-ID: <df3ead9fb0547531720b87f46821951f@quintile.net> (raw)
In-Reply-To: <412467dc08b91c236bd993a38c474e0c@coraid.com>
> 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.
>From my earlier example
eqn paper | cpu kremvax -c troff -ms >[2] errfile | cpu -c deepthought lp
will not put my troff errors in errfile, though I admit
this is becomming a rather contrived example.
I would like to be able to do:
rx -l steve host program > prog.out >[2] prog.err
and I cannot.
I thought about using cpu and putting a local filesystem MBEFORE
/dev/cons but it would have to make assumptions about the order
in which the remote cpu server opened /dev/cons (stdout and stderr)
which is a bit wooly for my liking.
Its not a big deal, I just wondered if there was a reason,
and I guess the answer is, no, no big reason, just no one
wanted it enough to do the work.
-Steve
next prev parent reply other threads:[~2007-01-20 1:15 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 [this message]
2007-01-20 1:34 ` erik quanstrom
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=df3ead9fb0547531720b87f46821951f@quintile.net \
--to=steve@quintile.net \
--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).