On Wed, Dec 15, 2021 at 07:13:49AM -0500, Neal Gompa wrote: > On Sat, Dec 11, 2021 at 5:43 AM Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: > > > > On Fri, Dec 10, 2021 at 05:03:45PM +0000, Richard W.M. Jones wrote: > > > On Fri, Dec 10, 2021 at 07:34:42AM +0000, Zbigniew Jędrzejewski-Szmek wrote: > > > > Also, I moved more stuff into the -udev subpackage: > > > > systemd-integritysetup, systemd-veritysetup, systemd-binfmt, > > > > systemd-sysctl, systemd-coredump. IIUC, none of those are useful > > > > in containers, so they fit better in -udev which is supposed to be installed > > > > on real hardware or VMs. > > > > > > Could we keep udev to being for udev and introduce a different package > > > for extras? This change affects libguestfs which only wants udev, not > > > systemd or anything else. > > > > Hmm, I don't think this changes anything for libguestfs. The > > systemd-udev rpm requires systemd, so if have systemd-udev, this is a > > noop. > > > > Please put systemd-coredump back in the main systemd package. Unlike > the others, this is actually required functionality for backtrace > stuff, especially if you're running OS containers (nspawn, ubi-init, > etc.). The handler for coredumps (/proc/sys/kernel/core_pattern) is not namespaced, so coredumps reported in a container are handled on the host (*). Are you sure that your coredump processing happens in the container? How does the pattern look like and how is the whole thing set up? (*) In principle systemd-coredump on the host could feed the core file back to some handler invoked in the container. We discussed this a few times in the past and it would be quite useful for some types of containers. But I'm not aware of this being implemented anywhere. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
