Re: redirection tricks on processor invocation

[Joan Picanyol i Puig <lists-supervision@biaix.org>]

* Joan Picanyol i Puig <lists-supervision@biaix.org> [20090603 12:31]:
> * Laurent Bercot <ska-supervision@skarnet.org> [20090603 08:27]:
> > > In summary, I want a copy of my processor's stdin to be seen by svlogd
> > > as my processor's stdout. Any ideas?
> > 
> >  Use multitee: http://code.dogmap.org/fdtools/multitee/
> > 
> >  Your processor could be, for instance, if you have execline installed:
> >  exec execlineb -c "
> >   piperw 6 7
> >   background { fdclose 7 fdmove 0 6 yourapplication }
> >   fdclose 6
> >   multitee 0-1,7
> >  "
> > 
> >  which copies stdin to stdout untouched, but also feeds a copy of
> > stdin to yourapplication's stdin.
> 
> Given that piperw apparently has no shell equivalent without a named
> pipe I guess it's time for me to bite the bullet and just use skalibs.

Actually, it's multitee's dependency in skalibs that makes me bite the
bullet (I should be able to avoid named pipes using subshells in my
processor's script.

qvb
--
pica