Re: [systemd-devel] systemd failing to close unwanted file descriptors & FDS spawning and crashing

2022-03-04 Thread Mantas Mikulėnas
On Fri, Mar 4, 2022 at 11:26 AM Christopher Obbard < chris.obb...@collabora.com> wrote: > Right, so it looks like the call to close_range fails. This is a 5.4 > kernel which doesn;t have close_range - so this is understandable. > No, if it was just a missing syscall, it would fail with -ENOSYS

Re: [systemd-devel] systemd failing to close unwanted file descriptors & FDS spawning and crashing

2022-03-04 Thread Christopher Obbard
Hi Lennart, On 04/03/2022 09:44, Lennart Poettering wrote: On Fr, 04.03.22 09:26, Christopher Obbard (chris.obb...@collabora.com) wrote: Right, so it looks like the call to close_range fails. This is a 5.4 kernel which doesn;t have close_range - so this is understandable. For a quick fix, I

[systemd-devel] Incomplete call stack logged by systemd-coredump

2022-03-04 Thread Ulrich Windl
Hi! In SLES15 SP3 I have found some interesting fact about systemd-coredump: A process dumped core for strange reasons (investigated by support), and the journal had logged: Mar 04 07:20:02 h19 systemd-coredump[27340]: Process 27338 (sh) of user 0 dumped core.

Re: [systemd-devel] systemd failing to close unwanted file descriptors & FDS spawning and crashing

2022-03-04 Thread Lennart Poettering
On Fr, 04.03.22 09:26, Christopher Obbard (chris.obb...@collabora.com) wrote: > Right, so it looks like the call to close_range fails. This is a 5.4 kernel > which doesn;t have close_range - so this is understandable. > > For a quick fix, I set have_close_range to false - see the patch attached.

Re: [systemd-devel] systemd failing to close unwanted file descriptors & FDS spawning and crashing

2022-03-04 Thread Christopher Obbard
Hi Mantas, On 03/03/2022 20:30, Mantas Mikulėnas wrote: Ah, right, I forgot – since this is done in the service child (right before exec) and not in the main process, you probably need to add the -f option to make strace follow forks... On Thu, Mar 3, 2022, 22:08 Christopher Obbard

Re: [systemd-devel] Antw: [EXT] Re: [systemd‑devel] How to find out the processes systemd‑shutdown is waiting for?

2022-03-04 Thread Lennart Poettering
On Fr, 04.03.22 08:20, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > >> Something seems to be off with containerd's integration into systemd but > >> I'm not sure what. > > > > Docker traditionally has not followed any of our documented ways to > > You are implying that "our

[systemd-devel] Antw: [EXT] [systemd‑devel] Q: journalctl ‑g

2022-03-04 Thread Ulrich Windl
>>> "Ulrich Windl" schrieb am 04.03.2022 um 08:07 in Nachricht <6221bac102a100048...@gwsmtp.uni-regensburg.de>: > Hi! > > In SLES15 SP3 (systemd‑246.16‑7.33.1.x86_64) I have this effect, wondering > whether it is a bug or a feature: > When using "journalctl ‑b ‑g raid" I see that _ome_

Re: [systemd-devel] Antw: [EXT] Re: [systemd‑devel] How to find out the processes systemd‑shutdown is waiting for?

2022-03-04 Thread Wols Lists
On 04/03/2022 07:20, Ulrich Windl wrote: Docker traditionally has not followed any of our documented ways to You are implying that "our documented ways" is a definitive standard? cgroups is a THIRD PARTY to both Docker and systemd. If Docker doesn't document what they're doing, how is

Re: [systemd-devel] Q: journalctl -g

2022-03-04 Thread Michael Chapman
On Fri, 4 Mar 2022, Ulrich Windl wrote: > Hi! > > In SLES15 SP3 (systemd-246.16-7.33.1.x86_64) I have this effect, wondering > whether it is a bug or a feature: > When using "journalctl -b -g raid" I see that _ome_ matches are highlighted > in red, but others aren't. For example: > Mar 01