From: "George Georgalis" <george@galis.org>
Subject: Re: Filtering socklog output revisited
Date: Fri, 1 Sep 2006 11:16:04 -0400 [thread overview]
Message-ID: <20060901151604.GE10960@run.galis.org> (raw)
In-Reply-To: <20060830144632.GM3979@run.galis.org>
On Wed, Aug 30, 2006 at 10:46:32AM -0400, George Georgalis wrote:
>On Wed, Aug 30, 2006 at 05:10:52AM +0200, Laurent Bercot wrote:
>> Why, what you need here is execline. :)
>> http://www.skarnet.org/software/execline/pipeline.html
>
>That looks pretty interesting.
>
>How would you use it to read (and conditionally process) fd1
>within a program (wrapper) that also reads fd0 and does a
>conditional exec with a fd0 and fd1 hand-off to a secondary
>program (qmail-queue)?
I don't see any way (with redirection) to use pipeline to manage
fd1 input within a script that already uses fd0 input.
Seems like a good c program, read input from an arbitrary fd
specified as a command line switch and pipe to stdout (where
it can be directed to an arbitrary fd, with the shell).
Seems all the shell redirection methods for "input" work on a
file. Or, is there a technique I'm missing?
// George
--
George Georgalis, systems architect, administrator <IXOYE><
next parent reply other threads:[~2006-09-01 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <loom.20060827T200142-606@post.gmane.org>
[not found] ` <20060828054124.GB12147@home.power>
[not found] ` <loom.20060830T004327-914@post.gmane.org>
[not found] ` <20060830011813.GB6449@home.power>
[not found] ` <20060830012814.GK3979@run.galis.org>
[not found] ` <20060830024505.GC6449@home.power>
[not found] ` <20060830031052.GA3462@skarnet.org>
[not found] ` <20060830144632.GM3979@run.galis.org>
2006-09-01 15:16 ` George Georgalis [this message]
2006-09-01 17:51 ` Matthew R. Dempsky
2006-09-02 2:27 ` George Georgalis
2006-11-11 20:42 ` George Georgalis
2006-11-12 5:36 ` George Georgalis
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=20060901151604.GE10960@run.galis.org \
--to=george@galis.org \
/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).