On Fri, Feb 04, 2022 at 02:06:02PM +, Laurent Bercot
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 filte
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
# logged
echo 'user.notice<13> 2022-02-04T12:41:14.832850+02:00 deb11-preseed 1K-TEST -
- - CTZjwuFcxITZj9HaFxK0Er4yskWkFoJd1pS106D4WvwoPTpXKIuRLJX5tzi8L0l3'
On Mon, Jan 05, 2015 at 09:21:06PM +0100, Laurent Bercot
wrote:
> On 05/01/2015 20:12, Caleb Spare wrote:
> >We're really happy with using runit/svlogd generally, but over time
> >we've found the TAI-timestamped filenames that svlogd produces, which
> >aren't human-readable, makes dealing with t
On Sun, Oct 19, 2014 at 11:29:38AM +0800, "Casper Ti. Vector"
wrote:
> Sorry if this is too off-topic, but I cannot figure out a reliable way
> to contact the author of nosh [1], so I put it here in the hope that the
> author may notice this:
>
> This patch fixes the following compilation error
Hi
I noticed that running s6-log as follows still creates few
archived logs:
s6-log -b s4096 n0 S0 !xz -0q /log
drwxr-x--- 5 s6log monitor 4096 Mar 22 16:36 .
drwxr-xr-x 6 root root 64 Mar 22 16:21 ..
drwxr-x--- 2 root root 118 Mar 22 16:10 env
drwx-wx-wt 2 root root 6 Mar 22 16
Hello
I am in the process of packaging up s6, installed to non-slashpackage
destination. s6-svwait tries to exec s6-ftrigrd, but it is not
available. This is part of strace -f s6-svwait output, s6-ftrigrd is
looked up correctly using the PATH value. As it currently stands
/command is symlinked to
