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