<refnamediv>
<refname>systemd.conf</refname>
- <refpurpose>systemd manager configuration file</refpurpose>
+ <refpurpose>System and service manager configuration file</refpurpose>
</refnamediv>
<refsynopsisdiv>
- <para><filename>system.conf</filename></para>
- <para><filename>user.conf</filename></para>
+ <para><filename>/etc/systemd/system.conf</filename></para>
+ <para><filename>/etc/systemd/user.conf</filename></para>
</refsynopsisdiv>
<refsect1>
<para>All options are configured in the
<literal>[Manager]</literal> section:</para>
- <variablelist>
+ <variablelist class='systemd-directives'>
<varlistentry>
<term><varname>LogLevel=</varname></term>
of controller names. Pass an empty
string to ensure that systemd does not
touch any hierarchies but its
- own.</para></listitem>
+ own.</para>
+
+ <para>Note that the default value of
+ 'cpu' will make realtime scheduling
+ unavailable to system services. See
+ <ulink
+ url="http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime">My
+ Service Can't Get Realtime!</ulink>
+ for more
+ information.</para></listitem>
</varlistentry>
<varlistentry>
- <term><varname>JoinControllers=cpu,cpuacct</varname></term>
+ <term><varname>JoinControllers=cpu,cpuacct,cpuset net_cls,netprio</varname></term>
<listitem><para>Configures controllers
that shall be mounted in a single
hierarchy. By default systemd will
mount all controllers which are
enabled in the kernel in individual
- hierachies, with the exception of
+ hierarchies, with the exception of
those listed in this setting. Takes a
space separated list of comma
separated controller names, in order
'cpu,cpuacct'. Pass an empty string to
ensure that systemd mounts all
controllers in separate
- hierarchies.</para></listitem>
+ hierarchies.</para>
+
+ <para>Note that this option is only
+ applied once, at very early boot. If
+ you use an initial RAM disk (initrd)
+ that uses systemd it might hence be
+ necessary to rebuild the initrd if
+ this option is changed, and make sure
+ the new configuration file is included
+ in it. Otherwise the initrd might
+ mount the controller hierachies in a
+ different configuration than intended,
+ and the main system cannot remount
+ them anymore.</para></listitem>
</varlistentry>
<varlistentry>
capabilities will be included, the
effect of the assignment
inverted. Note that this option also
- effects the respective capabilities in
+ affects the respective capabilities in
the effective, permitted and
inheritable capability sets. The
capability bounding set may also be
<listitem><para>Sets the timer slack
in nanoseconds for PID 1 which is then
inherited to all executed processes,
- unless overriden individually, for
+ unless overridden individually, for
example with the
<varname>TimerSlackNSec=</varname>
setting in service units (for details
<varname>infinity</varname> to
configure no limit on a specific
resource. These settings may be
- overriden in individual units
+ overridden in individual units
using the corresponding LimitXXX=
directives. Note that these resource
limits are only defaults for units,
<refsect1>
<title>See Also</title>
<para>
- <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+ <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
+ <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>
</para>
</refsect1>