From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19406 invoked from network); 4 Feb 2022 14:06:03 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 4 Feb 2022 14:06:03 -0000 Received: (qmail 28272 invoked by uid 89); 4 Feb 2022 14:06:28 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 28265 invoked from network); 4 Feb 2022 14:06:28 -0000 From: "Laurent Bercot" To: "Vallo Kallaste" , supervision@list.skarnet.org Subject: Re: s6-log weirdness Date: Fri, 04 Feb 2022 14:06:02 +0000 Message-Id: In-Reply-To: References: Reply-To: "Laurent Bercot" User-Agent: eM_Client/8.2.1659.0 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable >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