Re: [GIT PULL] kdbus for 4.1-rc1

[Mike Galbraith <umgwanakikbuti@gmail.com>]

On Wed, 2015-04-15 at 16:48 +0200, Michal Schmidt wrote:
> On 04/15/2015 09:31 AM, Mike Galbraith wrote:
> > it seems [systemd] has now mandated group scheduling.
> 
> What makes you think so? Was it the fact that by default you have a
> populated /sys/fs/cgroup/cpu/ hierarchy? This is either because some
> unit requests the use of the cpu controller using one of the CPU*=
> directives from systemd.resource-control(5), or (perhaps more likely)
> because there is a privileged unit with Delegate=yes. The most likely
> candidate is user@0.service, and so you could try preventing it from
> starting:
>   systemctl mask user@0.service

BTW, asking it to symlink it's disabled service to /dev/null, did 
indeed convince it to stop running said disabled service.

> Note that systemd still works without group scheduling or any cgroup
> subsystems enabled in the kernel:
> 
>   $ grep GROUP .config
>   CONFIG_CGROUPS=y

Yup.  CONFIG_CGROUPS=y all by itself isn't useless either, as that 
allows the user to use his box for something other than a doorstop.

Hohum, 'nuff of that ;-)

Thanks for the hint, it seems a tad dainbramaged, but it works.

        -Mike