[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120305124310.GD10929@tango.0pointer.de>
Date: Mon, 5 Mar 2012 13:43:10 +0100
From: Lennart Poettering <mzxreary@...inter.de>
To: Mike Galbraith <efault@....de>
Cc: Vivek Goyal <vgoyal@...hat.com>,
Michal Schmidt <mschmidt@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Tejun Heo <tj@...nel.org>, Li Zefan <lizf@...fujitsu.com>,
containers@...ts.linux-foundation.org, cgroups@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Kay Sievers <kay.sievers@...y.org>,
Frederic Weisbecker <fweisbec@...il.com>,
linux-kernel@...r.kernel.org, Christoph Hellwig <hch@...radead.org>
Subject: Re: [RFD] cgroup: about multiple hierarchies
On Thu, 01.03.12 23:04, Mike Galbraith (efault@....de) wrote:
>
> On Thu, 2012-03-01 at 16:02 -0500, Vivek Goyal wrote:
> > On Thu, Mar 01, 2012 at 09:26:43PM +0100, Mike Galbraith wrote:
>
> > > Q: you say systemd requires CONFIG_CGROUPS=y. Why is that? It's taking
> > > over sysvinits job afaiui, what does that have to do with cgroups?
> >
> > I think they were using it to track all the children forked by a service
> > and cleanup all of them if need be. So they just need it for logical
> > grouping functionality and don't require any controllers as such.
>
> Hm. Controllers are perhaps not required, but cpu controller was
> configured and used without consent. I didn't receive an offer.
Just set DefaultControllers= in /etc/systemd/system.conf to an empty
string and systemd will not make use of any hierarchy beyond its private
name=systemd named hierarchy.
Lennart
--
Lennart Poettering - Red Hat, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists