lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100513140354.GA12639@tango.0pointer.de>
Date:	Thu, 13 May 2010 16:03:54 +0200
From:	Lennart Poettering <mzxreary@...inter.de>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Dhaval Giani <dhaval.giani@...il.com>,
	James Kosin <jkosin@...comgrp.com>,
	linux-kernel@...r.kernel.org, menage@...gle.com,
	balbir@...ux.vnet.ibm.com, jsafrane@...hat.com, tglx@...utronix.de
Subject: Re: [PATCH/RFC] Have sane default values for cpusets

On Thu, 13.05.10 15:01, Peter Zijlstra (peterz@...radead.org) wrote:

> 
> On Wed, 2010-05-12 at 21:07 +0200, Lennart Poettering wrote:
> > See Dhaval's patch on the background of systemd
> > (http://0pointer.de/blog/projects/systemd.html). When a service is
> > started in systemd, we create a cgroup for it, when it ends, we remove
> > it. 
> 
> I seriously hope that's optional, because I for one would really hate a
> system that does that. I still mostly build kernels with only cpuset in
> and really don't want anybody but me creating groups in there.

By default systemd will create its groups in the "debug" hierarchy, (at
least for now, in the long run i'd like to see "noop" hierarchy or so,
that doesn't sound so temporary), since that controller is not useful
for anything but keeping track of processes. So it shouldn't bother you
at all.

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ