From: Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au>
To: supervision@list.skarnet.org
Subject: Re: s6-log problem with +regex
Date: Fri, 10 May 2019 14:52:57 +1000 [thread overview]
Message-ID: <a6b68a3a-4da2-e1e7-a874-b41b52d6fea7@heuristicsystems.com.au> (raw)
In-Reply-To: <em83b64206-0f16-4001-89b8-cc00424acf37@elzian>
Thank-you Guillermo & Laurent. I appreciate the detail, being a virgin
to daemontools this is a steep learning curve as I'm trying to ween off
monit.
The solution works nicely (& as intended) when using the workaround regex:
redirfd -r 0 /tmp/af
/usr/local/bin/s6-log n3 -.* +^a /tmp/a-only -.* +^b /tmp/b-only -.*
+^c /tmp/c-only -.* +^\\\[ /tmp/date-only f /tmp/default
However without any control directive, the result is:
s6-log: usage: s6-log [ -d notif ] [ -q | -v ] [ -b ] [ -p ] [ -t ] [ -e
] [ -l linelimit ] logging_script
Though running s6-log without a control directive is probably a little
silly, perhaps the requirement to have one may be worthwhile mentioning
in the doc.
Aside: I had orginally placed
ErrorLog "|/usr/local/bin/s6-log -b n32 s50000 S7000000
/var/log/httpd-error T !'/usr/bin/xz -7q' /var/log/httpd-error"
into apache24 which worked well in testing (one httpd), but of course in
production there are lots of httpd that do NOT use the parent for
logging errors, so locking is a problem.
Because I have three websites (3x error files, 3x access files) I was
looking at using 6 pipelines into two s6-log processes and regex's to
route the content. (hence my original example). Is this a good use of
resources or better to pipeline (funnel) to their own s6-log?
Kind regards, Dewayne.
next prev parent reply other threads:[~2019-05-10 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 1:02 Dewayne Geraghty
2019-05-10 2:27 ` Guillermo
2019-05-10 2:38 ` Laurent Bercot
2019-05-10 4:52 ` Dewayne Geraghty [this message]
2019-05-10 14:23 ` 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=a6b68a3a-4da2-e1e7-a874-b41b52d6fea7@heuristicsystems.com.au \
--to=dewayne.geraghty@heuristicsystems.com.au \
--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).