* s6-log weirdness
@ 2022-02-04 12:48 Vallo Kallaste
2022-02-04 14:06 ` Laurent Bercot
0 siblings, 1 reply; 3+ messages in thread
From: Vallo Kallaste @ 2022-02-04 12:48 UTC (permalink / raw)
To: supervision
[-- Attachment #1: Type: text/plain, Size: 140 bytes --]
Hi
I noticed that in some cases s6-log exits cleanly but does not log
anything. What's worse, it depends on the message content.
--
Vallo
[-- Attachment #2: asdasdf --]
[-- Type: text/plain, Size: 1057 bytes --]
# logged
echo 'user.notice<13> 2022-02-04T12:41:14.832850+02:00 deb11-preseed 1K-TEST - - - CTZjwuFcxITZj9HaFxK0Er4yskWkFoJd1pS106D4WvwoPTpXKIuRLJX5tzi8L0l3' |/usr/bin/s6-log n30 s10000000 '!zstd' -q /var/log/test
# not logged
echo 'user.notice<13> 2022-02-04T12:41:14.832850+02:00 deb11-preseed 1K-TEST - - - CTZjwuFcxITZj9HaFxK0Er4yskWkFoJd1pS106D4WvwoPTpXKIuRLJX5tzi8L0l3wXMrv7ESai47WLCpUSR3APom5WKf195ZReAH5JnqtH83c9uArY9fDMu5M3t4YTcA' |/usr/bin/s6-log n30 s10000000 '!zstd' -q /var/log/test
# logged
echo 'user.notice<13> 2022-02-04T12:41:14.832850+02:00 deb11-preseed 1K-TEST - - - CTZjwuFcxITZj9HaFxK0Er4yskWkFoJd1pS106D4WvwoPTpXKIuRLJX5tzi8L0l3wXMrv7ESai47WLCpUSR3APom5WKf195ZReAH5JnqtH83c9uArY9fDMu5M3t4YTcA' |/usr/bin/s6-log n30 s10000000 '!zstd -q' /var/log/test
# logged
echo 'user.notice<13> 2022-02-04T12:41:14.832850+02:00 deb11-preseed 1K-TEST - - - ================================================================================================================================' |/usr/bin/s6-log n30 s10000000 '!zstd' -q /var/log/test
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: s6-log weirdness
2022-02-04 12:48 s6-log weirdness Vallo Kallaste
@ 2022-02-04 14:06 ` Laurent Bercot
2022-02-04 15:25 ` Vallo Kallaste
0 siblings, 1 reply; 3+ messages in thread
From: Laurent Bercot @ 2022-02-04 14:06 UTC (permalink / raw)
To: Vallo Kallaste, supervision
>I noticed that in some cases s6-log exits cleanly but does not log
>anything. What's worse, it depends on the message content.
Hi Vallo,
That's the difference between '!zstd -q' and '!zstd' -q ;)
When -q isn't a part of your processor command, but a part of the
s6-log command line, it is interpreted as a selection directive,
and will filter anything that contains a 'q' character.
--
Laurent
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: s6-log weirdness
2022-02-04 14:06 ` Laurent Bercot
@ 2022-02-04 15:25 ` Vallo Kallaste
0 siblings, 0 replies; 3+ messages in thread
From: Vallo Kallaste @ 2022-02-04 15:25 UTC (permalink / raw)
To: supervision
On Fri, Feb 04, 2022 at 02:06:02PM +0000, Laurent Bercot
<ska-supervision@skarnet.org> wrote:
> Hi Vallo,
>
> That's the difference between '!zstd -q' and '!zstd' -q ;)
>
> When -q isn't a part of your processor command, but a part of the
> s6-log command line, it is interpreted as a selection directive,
> and will filter anything that contains a 'q' character.
Yes, that part I noticed, but it didn't occur to me that that lone '-q'
was taken as selector... Well, I feel dumb as a doorbell :)
It's been a while since I last touched s6.
The reason for lone '-q' was that I seem unable to give '!zstd -q' as
one argument in the rsyslogd omprog module configuration:
action(type="omprog" binary="/usr/bin/env - /usr/bin/s6-log -q n30 s10000000 !zstd -q /var/log/test" template="...)
Why? https://github.com/systemd/systemd/pull/21183#issuecomment-959799146
Compressed=yes and all, oh well...
--
Vallo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-02-04 15:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-04 12:48 s6-log weirdness Vallo Kallaste
2022-02-04 14:06 ` Laurent Bercot
2022-02-04 15:25 ` Vallo Kallaste
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).