On Saturday 21 June 2014 19:36:21 Yamaban wrote:
On Sat, 21 Jun 2014 16:37, Stefan Brüns
wrote: On Saturday 21 June 2014 12:53:31 Carlos E. R. wrote:
On 2014-06-21 05:12, Jan Engelhardt wrote:
You should really use a cgroup instead, where you can define exact usage quanta.
Since such already happens automatically (CONFIG_SCHED_AUTOGROUP), cron (and all its subprocesses) 's usage should be 1:n distributed with all logged-in users.
That's beyond my paycheck level :-)
Could you point to a "cgroup for dummies" docu somewhere? ;-)
cgroups in a systemd environment: http://0pointer.de/blog/projects/resources.html
Well, even https://en.wikipedia.org/wiki/Cgroups is more helpfull than Lennart's attempt at documentation.
[] you know the difference between a blog post and a man page
[sarcasm] Yeah, suuuuper handy. and ohhh sooo weeelll documented. -- NOT ! [/sarcasm]
man systemd.resource-control man systemd.scope man systemd.slice
Eitherway, a tool that allows to limit cpu, disk-io, net-io, and mem in one go is not available in default repo ATM. (e.g. [limit-tool-name] \ -c [cpu-limits:cores,percentage,nice] -d [disk-io-limits] \ -n [net-io-limits] -m [mem-limits] <command and args to run>])
man systemd-run Regards, Stefan PS: Stop ranting and educate yourself -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org