From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: systemd-253.5 regression
Date: Thu, 06 Jul 2023 09:15:54 +0100 [thread overview]
Message-ID: <877crdcv3q.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
systemd-253.5 backported a problematic commit which has since been
reverted in systemd master.
Please see https://github.com/systemd/systemd-stable/issues/302.
You'll need to backport https://github.com/systemd/systemd/pull/28000
which is a revert of the problematic change.
Quoting the revert commit:
"""
[...]
The change in question also breaks user level socket activation for
`podman.service` as the termination of the main `podman system service`
process is not properly handled, causing any application accessing the
socket to hang.
This is because the user-level `podman.service` unit also hosts two
non-main processes: `rootlessport` and `rootlessport-child` which causes
the `cgroup_good` check to still succeed.
[...]
"""
best,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
reply other threads:[~2023-07-06 8:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877crdcv3q.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=distributions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox