On Sat, 21 Jun 2014 16:37, Stefan Brüns
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. In short: either use a 3-rd Party tool to get the cgroup set up (e.g. https://en.wikipedia.org/wiki/Lmctfy) or do your own setup with the tools from libcgroup. [sarcasm] Yeah, suuuuper handy. and ohhh sooo weeelll documented. -- NOT ! [/sarcasm] 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>]) Maybe this could be the incentive to include such a tool in default repo, or even put it into the default install pattern. - Yamaban.