Le Sun, 12 Jan 2014 22:37:34 +0100,
Philipp Überbacher a écrit :
> On Sun, 12 Jan 2014 22:20:06 +0100 (CET)
No, in the same link I put in the first mail, Lennart say:
"In fact, I just prepped a patch to systemd to move every service and
every user session into its own cgroup in the 'cpu' hierarchy (in
addition to the group it already creates in the 'systemd' hierarchy). On
a system that runs systemd for both managing users and sessions this
means you are already half-way at what you want."
He concede this systemd patch is onhly half of what the kernel can do
when correctly used.
And he conclude:
"Well, if I make behaviour like this default in systemd, then this means
there won't be user setup for this. Because the distros shipping systemd
will get this as default behaviour."
His is talking about implementing in systemd something similar to the
automatic cgroups stuff if the kernel. For what I know, this is the
only thing that is implemented into systemd for the cgroups, and it is
only cosmetic possibilities to configure them with systemd.
This is way I also think we are not the only ones concerned, but any
body using something else than the automatic kernel cgroups stuff is
It is why I replaced debian by gentoo. It it even an udev fork,
eudev, which is udev without the crap. Some of my USE flags are
"-policykit -consolekit -udisks -udisks2 -pulseaudio", and I masked
udev and installed eudev instead.
Anyway, I launched another discussion on that topic on systemd
email list: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
As I understand it, the problem is related with a basic miss-conception
of what an user is doing with its computer. For peoples like Lennart (it
is other like him at freedesktop and in some distributions, and maybe
also elsewhere, the users are running a modern GUI. For them, it is 3 of
them, kde, gnome and xfce, and all other use cases are not relevant to
them. In other words, for them, an user doesn't work with its computer
but he is running a modern GUI.
Beside to not use systemd, the only solution to solve that mess is to
rewrite the cgroups API of systemd, so that it will support all the
cgroups features, and not only a subset, and so that the users can
configure it. Maybe he will put a java script interpreter into systemd