Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Lorenz]

Hi Felipe,

Felipe Sateler wrote:
> > > Upstream asks if cgroup is in v2-mode in the affected systems.
....
> With `findmnt -R /sys/fs/cgroup`. It should list controllers in the cgroup
> or cgroup2 filesystems.

root at lorenz:~# findmnt -R /sys/fs/cgroup
TARGET                   SOURCE  FSTYPE  OPTIONS
/sys/fs/cgroup           tmpfs   tmpfs   rw,nosuid,nodev,noexec,mode=755
├─/sys/fs/cgroup/unified cgroup2 cgroup2
rw,nosuid,nodev,noexec,relatime,nsdelegate
└─/sys/fs/cgroup/elogind cgroup  cgroup
rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/elogind/elogind-cgroups-agent,name=elogind


Il giorno lun 4 feb 2019 alle ore 16:11 Gedalya <gedalya at gedalya.net> ha
scritto:

>
> > This currently looks like this now (after I have uninstalled
> > cgroupfs-mount):
> >
> > → findmnt -R /sys/fs/cgroup
> > TARGET                   SOURCE  FSTYPE  OPTIONS
> > /sys/fs/cgroup           tmpfs   tmpfs   rw,nosuid,nodev,noexec,mode=755
> > ├─/sys/fs/cgroup/unified cgroup2 cgroup2
> rw,nosuid,nodev,noexec,relatime,nsdelegate
> > └─/sys/fs/cgroup/elogind cgroup  cgroup
> rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/elogind
> >
> > But I have to assume that these mount points where at least present
> > before I uninstalled cgroupfs-mount, too.
> >
> >               Regards, Axel
>
> I can say I've always had this issue with only cgroup2 mounted and no
> cgroup (what you might call "v1")
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190204/e6b0374a/attachment.html>