[systemd-devel] [ANNOUNCE] systemd 198

Holger Winkelmann hw at travelping.com
Thu Mar 7 21:31:45 PST 2013


Nice to see that... seems it was time for a release... ;-)

a few questions in line:

----- Original Message -----
> Hey!
> Finally, here's 198, with many big changes:
>         * Resource limits (as exposed by the various control group
>           controllers) can now be controlled dynamically at runtime
>           for all units. More specifically, you can now use a command
>           like "systemctl set-cgroup-attr foobar.service cpu.shares
>           2000" to alter the CPU shares a specific service gets. These
>           settings are stored persistently on disk, and thus allow the
>           administrator to easily adjust the resource usage of
>           services with a few simple commands. This dynamic resource
>           management logic is also available to other programs via the
>           bus. Almost any kernel cgroup attribute and controller is
>           supported.

Can you explain how the settings for a particular units are persistently
stored. Does systemd write back such values into the particular unit, or
are they stored somewhere else? The reason why I'm asking is the facts
that stuff like this strives the configuration management functions of
a Linux system.

The question would be:

How many configuration management should go into units? just bootstrapping
or also runtime changes or even runtime changes which going to be stored
persistently afterwards?

the later comes close to the MacOS "defaults write" command I think.


>         * The Python API of systemd now gained a new module for
>           reading journal files.

Are the problems with jumping to the end of the journal fixed?

Holger Winkelmann
email: hw at travelping.com
mobil: +49-171-5594745

More information about the systemd-devel mailing list