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.