On Sun, Oct 19, 2014 at 12:41 PM, James <wirel...@tampabay.rr.com> wrote: > Even if we all end up migrating to systemd (which from plentiful complaints > from many very bright folks about the net and the lack of a clean, useful > documentation on systemd, it's likely to be a decade before systemd > stablizes and folks produce sufficiently useful documentation and examples) > cgroups does illuminate how things should work in a complex environment so > it still is worth it's weight in gold, before one attempts to master the > (systemd) beast.
So, I realize there are many strong opinions regarding systemd, but this comes across a bit like, "one should be well-accustomed to building and operating a Linux-From-Scratch installation before one attempts to master the (Ubuntu) beast." Sure, all that auto-magic stuff does add complexity, but it does so with the goal of standardizing and automating this so that you can use the system without having to worry about all the details. If you are running a systemd service you can set the various cgroup controls like IO and CPU class/priority in the unit and it will take care of managing the cgroup for you. Certainly learning the nuts and bolts of how it all works is worthwhile - I wouldn't be running Gentoo if I felt otherwise. However, you really don't have to know how to build your own service manager to use one. As far as docs go - what specifically is unclear? Systemd is rapidly evolving so things do get out of date, but for the most part stuff like this can be found in man systemd.exec and such. Lennart's series of blog posts on system administration using systemd is a very good place to start. -- Rich
