From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gigabyte mobo latency
Date: Sun, 19 Oct 2014 14:56:26 -0400 [thread overview]
Message-ID: <CAGfcS_kS1F8V75C2N+TFCz-QuiZOrxCnw=Ae69BVR2DtTj-=DQ@mail.gmail.com> (raw)
In-Reply-To: <loom.20141019T171850-378@post.gmane.org>
On Sun, Oct 19, 2014 at 12:41 PM, James <wireless@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
next prev parent reply other threads:[~2014-10-19 18:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 15:49 [gentoo-user] gigabyte mobo latency James
2014-10-18 16:00 ` Volker Armin Hemmann
2014-10-18 16:26 ` [gentoo-user] " James
2014-10-18 19:27 ` Philip Webb
2014-10-18 20:24 ` Volker Armin Hemmann
2014-10-18 20:34 ` Neil Bothwick
2014-10-18 21:39 ` James
2014-10-19 11:25 ` Dale
2014-10-18 21:25 ` [gentoo-user] " thegeezer
2014-10-18 21:51 ` [gentoo-user] " James
2014-10-18 23:02 ` thegeezer
2014-10-19 3:15 ` James
2014-10-19 12:02 ` thegeezer
2014-10-19 16:41 ` James
2014-10-19 17:03 ` Dale
2014-10-19 20:03 ` James
2014-10-20 3:13 ` Dale
2014-10-19 18:56 ` Rich Freeman [this message]
2014-10-19 20:40 ` James
2014-10-19 20:57 ` Alan McKinnon
2014-10-19 21:35 ` Rich Freeman
2014-10-19 21:45 ` Volker Armin Hemmann
2014-10-19 23:34 ` Rich Freeman
2014-10-21 17:41 ` Volker Armin Hemmann
2014-10-22 1:35 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGfcS_kS1F8V75C2N+TFCz-QuiZOrxCnw=Ae69BVR2DtTj-=DQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox