Graham Anderson wrote:
On Saturday 29 Jun 2013 19:44:49 Linda Walsh wrote:
You mention it does it's own cgroup thing -- is that easy to shut off so it doesn't mess w/mine?
This should never be a problem. Systemd services run in a cgroup namespace directly mapped to the service name. So for example sshd runs under the "sshd.service" cgroup namespace.
You should probably read this mail about upcoming kernel and systemd changes with respect to cgroups, suffice it to say that there's going to be some significant changes so you may not want to rely too heavily on cgroup API's that might change in the not too distant future.
Um... *ouch*?
http://lists.freedesktop.org/archives/systemd-devel/2013-June/011521.html
--- I don't get it. I use the cgroups in /sys/fs/cgroup/. Currently my only usage is in the net_prio group to set default network priorities for a group or type of service (naming services, timekeeping, mail...etc). The only interface I'm aware of has been the one in /sys. They said something about there only being one hierarchy and it being owned by systemd. That sounds like it would interfere with setting anything up like I have already setup. What does it mean to own a hierarchy?? Are they removing the cgroup interface in /sys?
systemd is anything but monolithic, it's a collection of multiple specialised binaries, more than 50 of them... And they run with fairly tightly controlled kernel capabilities. What's the old adage, "do one thing and do it well", Does that sound familiar? ;)
Being in separate binaries doesn't mean it's _not_ monolithic. The linux kernel is 1 kernel but 100's or 1000's of modules. It is fairly configurable as to what is included. There are some large parts, but if you don't want, say, IPV6, you can build w/o it (as a random example). What type of boundaries are there between the binaries and is that interface "public" or did they they come up with their own internal interface that isn't based on any standard so nothing else can really tie in with them? Do they all require each other? Or are there are 50 different pieces one could choose to configure in like the 100's of modules in the kernel -- i.e. configuring in only the functionality that you want? If that's the case, that's cool, if not and it's an all or nothing thing... well, that'd tend to be more monolithic. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org