Re: Core dump of crashing service program

From: Liviu Nicoara <lnicoara_at_thinkoid.org>
Date: Sun, 14 Aug 2022 10:23:41 -0400

I am replying to this after the fact to clarify things.

On Tue, Aug 9, 2022 at 12:16 PM Laurent Bercot <ska-skaware_at_skarnet.org>
wrote:

> In order to change this default, you need to modify stage 1. This
> is dangerous, so pay attention to typos.
> After running s6-linux-init-maker and installing the result, edit
> your /etc/s6-linux-init/current/bin/init file. Normally this file
> is an execline script consisting of just one call to s6-linux-init
> with some options.
>

So, on my system the one-liner script that launches s6-linux-init ends
up being /sbin/s6-init. This I presume is the result of choices made by
Artix packaging (e.g., /etc/s6/current instead of
/etc/s6-linux-init/current). Anyhoo, the script /sbin/init after the mods
contains:

#!/usr/bin/execlineb -S0
s6-softlimit -c= --
s6-linux-init -c "/etc/s6/current" -m 0022 -p "/usr/bin:/bin" -- "$_at_"

The system boots normally and I have verified that s6-svscan (PID 1) has
unlimited core size.
Received on Sun Aug 14 2022 - 16:23:41 CEST

This archive was generated by hypermail 2.4.0 : Sun Aug 14 2022 - 16:23:54 CEST