[Bug 995956] Re: cgconfig upstart job should start earlier and mount all available cgroup types by default
urusha
995956 at bugs.launchpad.net
Wed May 9 08:16:28 UTC 2012
I see you. The critical issue is point 1, while point 2 is more a
configuration issue. Now after your explanation I agree with your
opinion about point 2. A better way is to add mount points
(cpuset,blkio) to the default configuration file. What should I do for
it then?
Well, I'm not against changing the title if it's needed.
The main purpose for me is to run daemons with limits. Upstart doesn't handle cgroups and cgroup limits at the moment, so the final optimal way I found is:
a) use cgconfig.conf to set limits
b) use service.override and cgexec to run daemon in the special cgroup. cups example:
exec cgexec -g cpuset:daemon-cups /usr/sbin/cupsd -F
cgred could also be used, but if you use lxc on the same machine it
affects all lxc container's daemons (cups) too and I don't need such
limits. Anyway point 1 of this bug report is needed for this method to
work too (cgconfig should start before cups).
Could you give me a link about libcgroup+libvirt problems?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.launchpad.net/bugs/995956
Title:
cgconfig upstart job should start earlier and mount all available
cgroup types by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/995956/+subscriptions
More information about the Ubuntu-server-bugs
mailing list