Hello,
Beneath the crunch heading, first paragraph, last sentence, the document
currently reads:
Chomping is off by default, or if you give the -c switch.
Should that 'Chomping' be 'Crunching'? i.e.:
-C/-c crunching on/off
-n/-N chomping on/off
Hello,
I stumbled on what might be an odd bug.
Most of our production workloads are containerised. We use Docker CE
for builds and execution on Linux. Outside of my day job, I have grown
quite fond of s6, and so it felt natural to make use of it in these
containerised environments.
On 4/2/2022 23:00, Laurent Bercot wrote:
So, SIGTERM does nothing because posix_spawn() is lying to s6-svscan,
pretending to have succeeded when it doesn't know it yet (and is going
to fail), and goading it into not doing anything. And it's lying
because something in qemu is messing with the
Hello,
Within the context of, say, an s6 run script that needs to do a little bit of
prep work before execing into a server, it is often helpful to abort early if
any of said prep work stumbles upon an unexpected problem.
Maybe the filesystem is R/O. Or full.
Maybe an operator has fat-fingered
On 6 Sep 2022, at 10:35, cat æscling via skaware wrote:
> using if instead of foreground sounds like what is wanted here
Indeed, thanks. That makes sense now that you mention it.
(I'm not entirely sure why my brain failed to make the connection.
Maybe because of preconceived notions of 'if'
