From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rx - wot no stderr?
Date: Fri, 19 Jan 2007 08:07:36 -0500 [thread overview]
Message-ID: <458a902e5883e2f125866013dbdd9fdf@coraid.com> (raw)
In-Reply-To: <599f06db0701190432qfd37963vce69c803d3ec67d1@mail.gmail.com>
rexexec(8) doesn't have anything to do with supporting stderr.
listen does this work. (assuming a p9 system not using ssh to connect.)
/sys/src/cmd/aux/listen.c:/^newcall dup(2)'s all three descriptors from
the incoming call. since it's a single Channel in the kernel, there's no way
to differentiate writes on fd 0, 1 or 2. if you want that, you need
to mux and demux the filedescriptors onto some protocol.
- erik
On Fri Jan 19 07:35:20 EST 2007, paurea@gmail.com wrote:
> On 1/17/07, Steve Simon <steve@quintile.net> wrote:
> > I was surprised to find plan9's implementaion of
> > rx(1) and rexexec(8) don't support a seperate socket
> > for stderr out of the remote application.
> >
> > I can see that it is not that great, but somtimes
> > when doing (from the manpage):
> >
> > eqn paper | rx kremvax troff -ms | rx deepthought lp
> >
> > It would be nice to see your troff error messages
> > onscreen rather than having to collect them from the
> > printer.
>
> I always survived this redirecting error messages to a file in
> the remote command. ¿Isn't that enough?.
> --
> - curiosity sKilled the cat
next prev parent reply other threads:[~2007-01-19 13:07 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 [this message]
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
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=458a902e5883e2f125866013dbdd9fdf@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).