[opensuse-factory] Wresting control from systemd
Greetings, Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed. Where does one find the config and on/off switch? marge:~ # cat /proc/$$/cgroup 9:perf_event:/ 8:blkio:/ 7:net_cls:/ 6:freezer:/ 5:devices:/ 4:memory:/ 3:cpuacct,cpu:/ 2:cpuset:/ 1:name=systemd:/user/root/66 That absolutely must die, but /etc/systemd/system.conf doesn't seem to be the right spot to kill it, as everything there is commented out. Also, 12.1 stole my /media mount point, and mounts it tmpfs. Where is that set up? Nuking it in init scripts didn't prevent it being mounted. Box seems determined to do it's own thing, but I'd like it do my thing instead, so need to find out how to talk to newfangled systemd gizmo. Guess I'll get used to systemd eventually, and maybe even become fond (ha) of it someday... but atm, it's just annoying. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 01 February 2012, Mike Galbraith wrote:
Greetings,
Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed. Where does one find the config and on/off switch?
Just switch back to sysvinit, see http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1 zypper in sysvinit-init zypper rm systemd-sysvinit
marge:~ # cat /proc/$$/cgroup 9:perf_event:/ 8:blkio:/ 7:net_cls:/ 6:freezer:/ 5:devices:/ 4:memory:/ 3:cpuacct,cpu:/ 2:cpuset:/ 1:name=systemd:/user/root/66
That absolutely must die, but /etc/systemd/system.conf doesn't seem to be the right spot to kill it, as everything there is commented out.
Also, 12.1 stole my /media mount point, and mounts it tmpfs. Where is that set up? Nuking it in init scripts didn't prevent it being mounted.
Box seems determined to do it's own thing, but I'd like it do my thing instead, so need to find out how to talk to newfangled systemd gizmo. Guess I'll get used to systemd eventually, and maybe even become fond (ha) of it someday... but atm, it's just annoying.
-Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 08:55 +0100, Ruediger Meier wrote:
On Wednesday 01 February 2012, Mike Galbraith wrote:
Greetings,
Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed. Where does one find the config and on/off switch?
Just switch back to sysvinit, see http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1
zypper in sysvinit-init zypper rm systemd-sysvinit
Ah, instant gratification. Thanks. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 01 of February 2012 08:55EN, Ruediger Meier wrote:
zypper in sysvinit-init zypper rm systemd-sysvinit
Any of these should do the other automatically as the packages conflict and both provide sbin_init which is necessary. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 01 février 2012 à 08:32 +0100, Mike Galbraith a écrit :
Greetings,
Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed.
You can't, cgroups are an integral part of systemd. But it doesn't prevent you to use them in conjunction of systemd cgroup (see http://www.freedesktop.org/wiki/Software/systemd/PaxControlGroups )
Also, 12.1 stole my /media mount point, and mounts it tmpfs. Where is that set up? Nuking it in init scripts didn't prevent it being mounted.
again, integral part of systemd. If you want to directories to be available in /media at startup, use a drop-in file in /etc/tmpfiles.d (see man tmpfiles.d for the syntax). -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 10:10 +0100, Frederic Crozat wrote:
Le mercredi 01 février 2012 à 08:32 +0100, Mike Galbraith a écrit :
Greetings,
Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed.
You can't, cgroups are an integral part of systemd.
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
But it doesn't prevent you to use them in conjunction of systemd cgroup (see http://www.freedesktop.org/wiki/Software/systemd/PaxControlGroups )
Also, 12.1 stole my /media mount point, and mounts it tmpfs. Where is that set up? Nuking it in init scripts didn't prevent it being mounted.
again, integral part of systemd. If you want to directories to be available in /media at startup, use a drop-in file in /etc/tmpfiles.d (see man tmpfiles.d for the syntax).
Thanks. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 01 février 2012 à 11:04 +0100, Mike Galbraith a écrit :
On Wed, 2012-02-01 at 10:10 +0100, Frederic Crozat wrote:
Le mercredi 01 février 2012 à 08:32 +0100, Mike Galbraith a écrit :
Greetings,
Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed.
You can't, cgroups are an integral part of systemd.
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
I don't see why, since it doesn't prevent you to use cgroup at all in your own liking, and bring a lot of nice features which would be hard (or impossible) to do without cgroup. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/02/12 07:04, Mike Galbraith wrote:
On Wed, 2012-02-01 at 10:10 +0100, Frederic Crozat wrote:
Le mercredi 01 février 2012 à 08:32 +0100, Mike Galbraith a écrit :
Greetings,
Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed.
You can't, cgroups are an integral part of systemd.
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
What's the problem with it ? how do you expect systemd to contain processes ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 09:04 -0300, Cristian Rodríguez wrote:
On 01/02/12 07:04, Mike Galbraith wrote:
On Wed, 2012-02-01 at 10:10 +0100, Frederic Crozat wrote:
Le mercredi 01 février 2012 à 08:32 +0100, Mike Galbraith a écrit :
Greetings,
Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed.
You can't, cgroups are an integral part of systemd.
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
What's the problem with it ? how do you expect systemd to contain processes ?
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Feb 1, 2012 at 10:30 AM, Mike Galbraith <mgalbraith@suse.de> wrote:
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
What's the problem with it ? how do you expect systemd to contain processes ?
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent.
I like bashing systemd too, but really I don't see your problem. You'll have to explain in more detail and without emotional language for us to understand. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 11:29 -0300, Claudio Freire wrote:
On Wed, Feb 1, 2012 at 10:30 AM, Mike Galbraith <mgalbraith@suse.de> wrote:
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
What's the problem with it ? how do you expect systemd to contain processes ?
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent.
I like bashing systemd too, but really I don't see your problem.
You'll have to explain in more detail and without emotional language for us to understand.
Not emotional, my problem has been resolved. My problem was that I need the ability to set my system up as I see fit, on the fly. I work on and test the scheduler quite a bit, including realtime stuff, and cannot have outside agencies making scheduler setup decisions for me. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/02/12 11:39, Mike Galbraith wrote: My problem was that I need
the ability to set my system up as I see fit, on the fly. I work on and test the scheduler quite a bit, including realtime stuff, and cannot have outside agencies making scheduler setup decisions for me.
Ah, Ok, I initially thought you were experiencing a bug, is just yet another case of "It does things differently from the way I want, to cover my corner use case" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2/1/2012 9:46 AM, Cristian Rodríguez wrote:
On 01/02/12 11:39, Mike Galbraith wrote: My problem was that I need
the ability to set my system up as I see fit, on the fly. I work on and test the scheduler quite a bit, including realtime stuff, and cannot have outside agencies making scheduler setup decisions for me.
Ah, Ok, I initially thought you were experiencing a bug, is just yet another case of "It does things differently from the way I want, to cover my corner use case"
The world is made up of "corner" use cases. Covering the most common case at the expense of the others is crap. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 11:46 -0300, Cristian Rodríguez wrote:
On 01/02/12 11:39, Mike Galbraith wrote: My problem was that I need
the ability to set my system up as I see fit, on the fly. I work on and test the scheduler quite a bit, including realtime stuff, and cannot have outside agencies making scheduler setup decisions for me.
Ah, Ok, I initially thought you were experiencing a bug, is just yet another case of "It does things differently from the way I want, to cover my corner use case"
That's completely wrong. Systemd silently and insistently broke a perfectly valid usage. The little bugger is gone, I'm happy. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Feb 1, 2012 at 12:33 PM, Mike Galbraith <mgalbraith@suse.de> wrote:
Ah, Ok, I initially thought you were experiencing a bug, is just yet another case of "It does things differently from the way I want, to cover my corner use case"
That's completely wrong. Systemd silently and insistently broke a perfectly valid usage. The little bugger is gone, I'm happy.
How did it break. As far as I know[0], you're still free to create new cgroups within systemd's hierarchy. [0] http://www.kernel.org/doc/Documentation/cgroups/cgroups.txt -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 13:18 -0300, Claudio Freire wrote:
As far as I know[0], you're still free to create new cgroups within systemd's hierarchy.
[0] http://www.kernel.org/doc/Documentation/cgroups/cgroups.txt
Why do I have to co-exist with a cgroup heirarchy that is useless to me at best? If you can configure/control the thing, cool, but I was told you cannot turn it off. That makes it completely unacceptable. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Mike Galbraith wrote:
another case of "It does things differently from the way I want, to cover my corner use case" That's completely wrong. Systemd silently and insistently broke a
Ah, Ok, I initially thought you were experiencing a bug, is just yet perfectly valid usage. The little bugger is gone, I'm happy.
I also have removed systemd from 2 of my systems, as I couldn't afford to work around a broken system. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2012-02-01 at 16:33 +0100, Mike Galbraith wrote:
That's completely wrong. Systemd silently and insistently broke a perfectly valid usage. The little bugger is gone, I'm happy.
Not for long. You will not be able to disable systemd sometime in the future (date unknown yet), so you'd better make up your case without emotional language so that you can also solve your problem when that time comes. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk8pysEACgkQtTMYHG2NR9U/ngCgicfPkEF150A21VDwSclbrSSX EEYAn1VVMvt0o36bTlGojKUOfKXUMoSY =FFYp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2012-02-02 at 00:28 +0100, Carlos E. R. wrote:
On Wednesday, 2012-02-01 at 16:33 +0100, Mike Galbraith wrote:
That's completely wrong. Systemd silently and insistently broke a perfectly valid usage. The little bugger is gone, I'm happy.
Not for long.
You will not be able to disable systemd sometime in the future (date unknown yet), so you'd better make up your case without emotional language so that you can also solve your problem when that time comes.
I simply asked how I can regain the control I need, was told I can't, that there is no option other than to remove systemd, so I did that. If at some point regaining control requires digging into the source, I'll either do that, or change to a distro that still understands that users expect software to be a well behaved slave, not their master. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 02 of February 2012 00:28EN, Carlos E. R. wrote:
You will not be able to disable systemd sometime in the future (date unknown yet),
Well, again: was this already decided? If yes, who and when decided it? If not, please don't present your wishes as given facts. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2012-02-02 at 09:29 +0100, Michal Kubeček wrote:
On Thursday 02 of February 2012 00:28EN, Carlos E. R. wrote:
You will not be able to disable systemd sometime in the future (date unknown yet),
Well, again: was this already decided? If yes, who and when decided it? If not, please don't present your wishes as given facts.
I hope we never become that short-sighted. Offering an automated cgroups setup is nice, ramming it down the user's throat is not. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Donnerstag, 2. Februar 2012, 09:39:44 schrieb Mike Galbraith:
On Thu, 2012-02-02 at 09:29 +0100, Michal Kubeček wrote:
Well, again: was this already decided? If yes, who and when decided it? If not, please don't present your wishes as given facts.
I hope we never become that short-sighted. Offering an automated cgroups setup is nice, ramming it down the user's throat is not.
Since openSUSE is open, you just need to find a long-term maintainer for all sysvinit issues and packaging and contribute that package to the distro. If openSUSE staff provides one you are lucky, if not it's up to the community, i.e. those that need that package. I guess it's all about demand and supply for feature x or package y. Limited resources make it impossible to serve each and everybody. Sven -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-02-02 09:29, Michal Kubeček wrote:
On Thursday 02 of February 2012 00:28EN, Carlos E. R. wrote:
You will not be able to disable systemd sometime in the future (date unknown yet),
Well, again: was this already decided? If yes, who and when decided it? If not, please don't present your wishes as given facts.
It is not my wish, rather against my wishes. I simply accept /facts/. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk8qaa8ACgkQtTMYHG2NR9XjcQCfbLzjyC7Pmf6ISHIwAYHSM6Rc H+MAoJV40QrgmqP5cVSdMoujusry+gLY =fbNK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mercredi 01 février 2012 à 15:39 +0100, Mike Galbraith a écrit :
On Wed, 2012-02-01 at 11:29 -0300, Claudio Freire wrote:
On Wed, Feb 1, 2012 at 10:30 AM, Mike Galbraith <mgalbraith@suse.de> wrote:
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
What's the problem with it ? how do you expect systemd to contain processes ?
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent.
I like bashing systemd too, but really I don't see your problem.
You'll have to explain in more detail and without emotional language for us to understand.
Not emotional, my problem has been resolved. My problem was that I need the ability to set my system up as I see fit, on the fly. I work on and test the scheduler quite a bit, including realtime stuff, and cannot have outside agencies making scheduler setup decisions for me.
And it didn't work by changing : in /etc/systemd/system.conf : DefaultControllers= JoinControllers= and in /etc/systemd/systemd-logind.conf ResetControllers= ? (not tested) -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 15:50 +0100, Frederic Crozat wrote:
Le mercredi 01 février 2012 à 15:39 +0100, Mike Galbraith a écrit :
On Wed, 2012-02-01 at 11:29 -0300, Claudio Freire wrote:
On Wed, Feb 1, 2012 at 10:30 AM, Mike Galbraith <mgalbraith@suse.de> wrote:
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
What's the problem with it ? how do you expect systemd to contain processes ?
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent.
I like bashing systemd too, but really I don't see your problem.
You'll have to explain in more detail and without emotional language for us to understand.
Not emotional, my problem has been resolved. My problem was that I need the ability to set my system up as I see fit, on the fly. I work on and test the scheduler quite a bit, including realtime stuff, and cannot have outside agencies making scheduler setup decisions for me.
And it didn't work by changing : in /etc/systemd/system.conf : DefaultControllers= JoinControllers=
and in /etc/systemd/systemd-logind.conf ResetControllers=
? (not tested)
That's what grep led me to, but everything in there was commented out, so I figured it must be controlled elsewhere. Too late to test stuff now, it's toast, and I can't afford to put it back and futz with it. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 14:30 +0100, Mike Galbraith wrote:
On Wed, 2012-02-01 at 09:04 -0300, Cristian Rodríguez wrote:
On 01/02/12 07:04, Mike Galbraith wrote:
On Wed, 2012-02-01 at 10:10 +0100, Frederic Crozat wrote:
Le mercredi 01 février 2012 à 08:32 +0100, Mike Galbraith a écrit :
Greetings,
Recovering from a completely disasterous update to 12.1, I find that systemd has automated cgroups. This is less than useless to me, I need to turn this stuff off so I can set things up as needed, when needed.
You can't, cgroups are an integral part of systemd.
Incredible. Until now, systemd sounded to me like it might be a step in the right direction. It suddenly sounds utterly vile.
What's the problem with it ? how do you expect systemd to contain processes ?
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent.
BTW, imagine I posted a patch removing SCHED_AUTOGROUP option, mandating that anyone who has CGROUP_SCHED enabled WILL use automated task groups as the great and powerful me (arrogance personified) defines them. The world would burn little 'ole /me at the stake, and rightfully so. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/02/12 11:35, Mike Galbraith wrote:
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent.
So essentially what are you asking is no one taking design decisions ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2012-02-01 at 11:52 -0300, Cristian Rodríguez wrote:
On 01/02/12 11:35, Mike Galbraith wrote:
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent.
So essentially what are you asking is no one taking design decisions ?
No, I will not split hairs with you. Systemd completely broke my usage. Full stop. Systemd is history because of that. Full stop. -Mike -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 01 of February 2012 11:52EN, Cristian Rodríguez wrote:
On 01/02/12 11:35, Mike Galbraith wrote:
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent. So essentially what are you asking is no one taking design decisions ?
Taking design decisions doesn't necessarily mean taking the choice away from users. If systemd started each service in its cgroup by default (but would allow to switch it off), it would be just a design decision. Starting each service in its cgroup and not giving an option to switch this behaviour off is taking the freedom of choice away from users. Fortunately, there is still possibility not to use systemd at all (without having to switch distribution, that is). Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/02/12 13:50, Michal Kubeček wrote:
On Wednesday 01 of February 2012 11:52EN, Cristian Rodríguez wrote:
On 01/02/12 11:35, Mike Galbraith wrote:
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent. So essentially what are you asking is no one taking design decisions ?
Taking design decisions doesn't necessarily mean taking the choice away from users. If systemd started each service in its cgroup by default (but would allow to switch it off), it would be just a design decision. Starting each service in its cgroup and not giving an option to switch this behaviour off is taking the freedom of choice away from users.
that's what ControlGroup= option is for, the user can select in what cgroup the service runs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 01 Feb 2012 15:35:01 Mike Galbraith wrote:
I expect it to do process containment when and how I says it's ok to do so. It is not at all cool for systemd to do what someone else decides it should do with my processes in my workstation without my consent.
BTW, imagine I posted a patch removing SCHED_AUTOGROUP option, mandating that anyone who has CGROUP_SCHED enabled WILL use automated task groups as the great and powerful me (arrogance personified) defines them. The world would burn little 'ole /me at the stake, and rightfully so.
Perhaps the software that automatically offers greater flexibility and control over processes is more valuable to more people than the software that automatically lets processes run glxgears at 50k fps without dropping a couple of frames of southpark. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (12)
-
Brian K. White -
Carlos E. R. -
Carlos E. R. -
Claudio Freire -
Cristian Rodríguez -
Frederic Crozat -
Graham Anderson -
James Knott -
Michal Kubeček -
Mike Galbraith -
Ruediger Meier -
Sven Burmeister