From: Joan Picanyol i Puig <lists-supervision@biaix.org>
To: supervision@list.skarnet.org
Subject: redirection tricks on processor invocation
Date: Tue, 2 Jun 2009 12:48:20 +0200 [thread overview]
Message-ID: <20090602104820.GB80818@grummit.biaix.org> (raw)
Dear all,
I have an application that generates aggregate reports from separate
log streams. In order to avoid loosing data, it should be invoked as a
processor from all of it's sources log directories. The application
reads from stdin (and thus know what stream it is called from and what
other streams should look at). However, I don't the resultant log file
to be altered (since I must archive it for auditing purposes).
I've been struggling to find the correct fd copying and redirections so
that whenever runit feeds @*.u to my processor a copy of it is sent to
stdout (the application writes to a separate location), but to no avail.
In summary, I want a copy of my processor's stdin to be seen by svlogd
as my processor's stdout. Any ideas?
tks
--
pica
next reply other threads:[~2009-06-02 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 10:48 Joan Picanyol i Puig [this message]
2009-06-03 6:26 ` Laurent Bercot
2009-06-03 10:31 ` Joan Picanyol i Puig
2009-06-03 10:38 ` Joan Picanyol i Puig
2009-06-12 11:48 ` Joan Picanyol i Puig
2009-06-13 5:13 ` Laurent Bercot
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=20090602104820.GB80818@grummit.biaix.org \
--to=lists-supervision@biaix.org \
--cc=supervision@list.skarnet.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).