shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-02 10:51:20 +03:00
Code
d081dffbd3
systemd/man/systemd.conf.xml

285 lines
15 KiB
XML
Raw Normal View History

update man pages for recent changes
2010-07-07 03:38:56 +04:00
<?xml version='1.0'?> <!--*-nxml-*-->
<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2010 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 02:20:58 +04:00
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
update man pages for recent changes
2010-07-07 03:38:56 +04:00
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 02:20:58 +04:00
Lesser General Public License for more details.
update man pages for recent changes
2010-07-07 03:38:56 +04:00
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 02:20:58 +04:00
You should have received a copy of the GNU Lesser General Public License
update man pages for recent changes
2010-07-07 03:38:56 +04:00
along with systemd; If not, see <http://www.gnu.org/licenses/>.
-->
<refentry id="systemd.conf">
<refentryinfo>
<title>systemd.conf</title>
<productname>systemd</productname>
<authorgroup>
<author>
<contrib>Developer</contrib>
<firstname>Lennart</firstname>
<surname>Poettering</surname>
<email>lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta>
<refentrytitle>systemd.conf</refentrytitle>
<manvolnum>5</manvolnum>
</refmeta>
<refnamediv>
<refname>systemd.conf</refname>
<refpurpose>systemd manager configuration file</refpurpose>
</refnamediv>
<refsynopsisdiv>
<para><filename>system.conf</filename></para>
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 00:12:41 +03:00
<para><filename>user.conf</filename></para>
update man pages for recent changes
2010-07-07 03:38:56 +04:00
</refsynopsisdiv>
<refsect1>
<title>Description</title>
<para>When run as system instance systemd reads the
configuration file <filename>system.conf</filename>,
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 00:12:41 +03:00
otherwise <filename>user.conf</filename>. These
update man pages for recent changes
2010-07-07 03:38:56 +04:00
configuration files contain a few settings controlling
basic manager operations.</para>
</refsect1>
<refsect1>
<title>Options</title>
<para>All options are configured in the
<literal>[Manager]</literal> section:</para>
<variablelist>
<varlistentry>
<term><varname>LogLevel=</varname></term>
<term><varname>LogTarget=</varname></term>
<term><varname>LogColor=</varname></term>
<term><varname>LogLocation=</varname></term>
<term><varname>DumpCore=yes</varname></term>
<term><varname>CrashShell=no</varname></term>
<term><varname>ShowStatus=yes</varname></term>
<term><varname>CrashChVT=1</varname></term>
journal: introduce log target 'journal' for executed processes
2012-01-06 02:54:45 +04:00
<term><varname>DefaultStandardOutput=journal</varname></term>
exec: introduce global defaults for the standard output of services
2011-02-15 13:52:29 +03:00
<term><varname>DefaultStandardError=inherit</varname></term>
update man pages for recent changes
2010-07-07 03:38:56 +04:00
<listitem><para>Configures various
parameters of basic manager
operation. These options may be
man: remaining spelling fixes
2010-12-31 03:50:51 +03:00
overridden by the respective command
update man pages for recent changes
2010-07-07 03:38:56 +04:00
line arguments. See
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
for details about these command line
arguments.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>CPUAffinity=</varname></term>
<listitem><para>Configures the initial
CPU affinity for the init
man: Fix small typo: s/seperate/separate/
2010-09-03 18:30:48 +04:00
process. Takes a space-separated list
update man pages for recent changes
2010-07-07 03:38:56 +04:00
of CPU indexes.</para></listitem>
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 00:12:41 +03:00
</varlistentry>
manager: make list of default controllers configurable
2010-11-18 02:42:35 +03:00
<varlistentry>
<term><varname>DefaultControllers=cpu</varname></term>
<listitem><para>Configures in which
cgroup controller hierarchies to
create per-service cgroups
automatically, in addition to the
name=systemd named hierarchy. Defaults
man: remaining spelling fixes
2010-12-31 03:50:51 +03:00
to 'cpu'. Takes a space separated list
manager: make list of default controllers configurable
2010-11-18 02:42:35 +03:00
of controller names. Pass an empty
string to ensure that systemd does not
man: remaining spelling fixes
2010-12-31 03:50:51 +03:00
touch any hierarchies but its
manager: make list of default controllers configurable
2010-11-18 02:42:35 +03:00
own.</para></listitem>
</varlistentry>
cgroup: optionally mount a specific cgroup controllers together, and add cpu+cpuacct to the default
2011-08-23 02:37:35 +04:00
<varlistentry>
<term><varname>JoinControllers=cpu,cpuacct</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
those listed in this setting. Takes a
space separated list of comma
separated controller names, in order
to allow multiple joined
hierarchies. Defaults to
'cpu,cpuacct'. Pass an empty string to
ensure that systemd mounts all
controllers in separate
hierarchies.</para></listitem>
</varlistentry>
systemd: add hardware watchdog support This adds minimal hardware watchdog support to PID 1. The idea is that PID 1 supervises and watchdogs system services, while the hardware watchdog is used to supervise PID 1. This adds two hardware watchdog configuration options, for the runtime watchdog and for a shutdown watchdog. The former is active during normal operation, the latter only at reboots to ensure that if a clean reboot times out we reboot nonetheless. If the runtime watchdog is enabled PID 1 will automatically wake up at half the configured interval and write to the watchdog daemon. By default we enable the shutdown watchdog, but leave the runtime watchdog disabled in order not to break independent hardware watchdog daemons people might be using. This is only the most basic hookup. If necessary we can later on hook up the watchdog ping more closely with services deemed crucial.
2012-04-06 00:08:10 +04:00
<varlistentry>
<term><varname>RuntimeWatchdogSec=</varname></term>
<term><varname>ShutdownWatchdogSec=</varname></term>
<listitem><para>Configure the hardware
watchdog at runtime and at
reboot. Takes a timeout value in
seconds (or in other time units if
suffixed with <literal>ms</literal>,
<literal>min</literal>,
<literal>h</literal>,
<literal>d</literal>,
<literal>w</literal>). If
<varname>RuntimeWatchdogSec=</varname>
is set to a non-zero value the
watchdog hardware
(<filename>/dev/watchdog</filename>)
will be programmed to automatically
reboot the system if it is not
contacted within the specified timeout
interval. The system manager will
ensure to contact it at least once in
half the specified timeout
interval. This feature requires a
hardware watchdog device to be
present, as it is commonly the case in
embedded and server systems. Not all
hardware watchdogs allow configuration
of the reboot timeout, in which case
the closest available timeout is
picked. <varname>ShutdownWatchdogSec=</varname>
may be used to configure the hardware
watchdog when the system is asked to
reboot. It works as a safety net to
ensure that the reboot takes place
even if a clean reboot attempt times
out. By default
<varname>RuntimeWatchdogSec=</varname>
defaults to 0 (off), and
<varname>ShutdownWatchdogSec=</varname>
to 10min. These settings have no
effect if a hardware watchdog is not
available.</para></listitem>
</varlistentry>
main: allow system wide limits for services
2012-03-21 21:03:40 +04:00
main: add configuration option to alter capability bounding set for PID 1 This also ensures that caps dropped from the bounding set are also dropped from the inheritable set, to be extra-secure. Usually that should change very little though as the inheritable set is empty for all our uses anyway.
2012-05-24 06:00:56 +04:00
<varlistentry>
<term><varname>CapabilityBoundingSet=</varname></term>
<listitem><para>Controls which
capabilities to include in the
capability bounding set for PID 1 and
its children. See
<citerefentry><refentrytitle>capabilities</refentrytitle><manvolnum>7</manvolnum></citerefentry>
for details. Takes a whitespace
separated list of capability names as
read by
<citerefentry><refentrytitle>cap_from_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
Capabilities listed will be included
in the bounding set, all others are
removed. If the list of capabilities
is prefixed with ~ all but the listed
capabilities will be included, the
effect of the assignment
inverted. Note that this option also
effects the respective capabilities in
the effective, permitted and
inheritable capability sets. The
capability bounding set may also be
individually configured for units
using the
<varname>CapabilityBoundingSet=</varname>
directive for units, but note that
capabilities dropped for PID 1 cannot
be regained in individual units, they
are lost for good.</para></listitem>
</varlistentry>
main: allow setting of timer slack for PID 1
2012-05-31 06:36:08 +04:00
<varlistentry>
<term><varname>TimerSlackNSec=</varname></term>
<listitem><para>Sets the timer slack
in nanoseconds for PID 1 which is then
inherited to all executed processes,
unless overriden individually, for
example with the
<varname>TimerSlackNSec=</varname>
setting in service units (for details
see
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>). The
timer slack controls the accuracy of
wake-ups triggered by timers. See
<citerefentry><refentrytitle>prctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
for more information. Note that in
contrast to most other time span
definitions this parameter takes an
integer value in nano-seconds if no
unit is specified. The usual time
units are understood
too.</para></listitem>
</varlistentry>
main: allow system wide limits for services
2012-03-21 21:03:40 +04:00
<varlistentry>
<term><varname>DefaultLimitCPU=</varname></term>
<term><varname>DefaultLimitFSIZE=</varname></term>
<term><varname>DefaultLimitDATA=</varname></term>
<term><varname>DefaultLimitSTACK=</varname></term>
<term><varname>DefaultLimitCORE=</varname></term>
<term><varname>DefaultLimitRSS=</varname></term>
<term><varname>DefaultLimitNOFILE=</varname></term>
<term><varname>DefaultLimitAS=</varname></term>
<term><varname>DefaultLimitNPROC=</varname></term>
<term><varname>DefaultLimitMEMLOCK=</varname></term>
<term><varname>DefaultLimitLOCKS=</varname></term>
<term><varname>DefaultLimitSIGPENDING=</varname></term>
<term><varname>DefaultLimitMSGQUEUE=</varname></term>
<term><varname>DefaultLimitNICE=</varname></term>
<term><varname>DefaultLimitRTPRIO=</varname></term>
<term><varname>DefaultLimitRTTIME=</varname></term>
main: add configuration option to alter capability bounding set for PID 1 This also ensures that caps dropped from the bounding set are also dropped from the inheritable set, to be extra-secure. Usually that should change very little though as the inheritable set is empty for all our uses anyway.
2012-05-24 06:00:56 +04:00
main: allow system wide limits for services
2012-03-21 21:03:40 +04:00
<listitem><para>These settings control
main: add configuration option to alter capability bounding set for PID 1 This also ensures that caps dropped from the bounding set are also dropped from the inheritable set, to be extra-secure. Usually that should change very little though as the inheritable set is empty for all our uses anyway.
2012-05-24 06:00:56 +04:00
various default resource limits for
units. See
main: allow system wide limits for services
2012-03-21 21:03:40 +04:00
<citerefentry><refentrytitle>setrlimit</refentrytitle><manvolnum>2</manvolnum></citerefentry>
for details. Use the string
<varname>infinity</varname> to
configure no limit on a specific
main: add configuration option to alter capability bounding set for PID 1 This also ensures that caps dropped from the bounding set are also dropped from the inheritable set, to be extra-secure. Usually that should change very little though as the inheritable set is empty for all our uses anyway.
2012-05-24 06:00:56 +04:00
resource. These settings may be
overriden in individual units
using the corresponding LimitXXX=
directives. Note that these resource
limits are only defaults for units,
they are not applied to PID 1
itself.</para></listitem>
main: allow system wide limits for services
2012-03-21 21:03:40 +04:00
</varlistentry>
update man pages for recent changes
2010-07-07 03:38:56 +04:00
</variablelist>
</refsect1>
<refsect1>
<title>See Also</title>
<para>
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
</para>
</refsect1>
</refentry>
Copy Permalink