On 8/4/2019 9:26 AM, Pierre Labastie via blfs-dev wrote:
t would be useful.
Concerning cgroup v2, "man cgroups" tells:
"Note that on many modern systems, systemd(1) automatically mounts the
cgroup2 filesystem at /sys/fs/cgroup/unified during the boot process".
According to what I see, elogind does that too.
Well, that is definitely new functionality from when I first started on
it then. One of the first questions was if this and that exist in the
paths mentioned when troubleshooting. If both cgroups mounts are handled
automatically, then let's drop mountcgroupfs. I'll be able to reboot in
an hour or two on a completed system and do the secondary confirmation
for you, plus it'll give me a quick test of new scripts. What do you
think about the elogind scirpt? Drop it? I do not know if the cgroup
fallback is true for elogind, but would expect so since it's from the
same codebase (have to test with a kernel that is not prepared for
cgroups, but even so, I suspect the only lost functionality is the quick
cleanup of user processes).
--DJ
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
