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, [EMAIL PROTECTED] wrote: > On 1/17/07, Steve Simon <[EMAIL PROTECTED]> 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
