Re: [systemd-devel] Empty /sys/fs/cgroup/cpu directory post reboot

[Michal Koutný]

Hello Tarana.

On Wed, Sep 11, 2019 at 12:17:51PM +, " TARANA, YASHASHVI " 
 wrote:
> I noticed that, once,  after reboot, the directory /sys/fs/cgroup/cpu
> was empty.
The directories for indvidual cgroups are only created based on demand
(the directory path suggests you use the legacy or hybrid hierarchy).
Any unit which requires some of the CPU controller functionality will
trigger building of the hierarchy. By contrast, if there is no such
unit, systemd will not bother creating the directories for the CPU
hierarchy.

> However, after rebooting again, it once again had the original
> contents.
It seems that the latter boot must have started a unit that wasn't
active before and that required the CPU controller.

HTH,
Michal


signature.asc
Description: Digital signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Empty /sys/fs/cgroup/cpu directory post reboot

[TARANA, YASHASHVI]

Hello,


I noticed that, once,  after reboot, the directory /sys/fs/cgroup/cpu was 
empty. However, after rebooting again, it once again had the original contents. 
Has anyone else noticed this behavior?

Regards,
Yashashvi

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel