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
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 -.*
Thank-you for s6-rc and friends. I came across two items:
1. the s6-log in testing requires a control directive. In my testing
without a T, t, n $VALUE for example, the s6-log command failed.
"s6-log 1", which does nothing but send stdin straight through to
stdout, works for me on both Linux
Hi,
El jue., 9 may. 2019 a las 22:03, Dewayne Geraghty escribió:
>
> My test comprised an input /tmp/af with the intention of
> four separate s6-log managed logdirs. The logdirs' structure was
> correctly created, however three contained the same content, and the
> default contained nothing. So
Thank-you for s6-rc and friends. I came across two items:
1. the s6-log in testing requires a control directive. In my testing
without a T, t, n $VALUE for example, the s6-log command failed.
2. The regular expression preceded by a + unintentionally matches
everything, which was surprising as I
