man/systemd-user.conf.html

   1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>systemd-system.conf</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><style>
   2     a.headerlink {
   3       color: #c60f0f;
   4       font-size: 0.8em;
   5       padding: 0 4px 0 4px;
   6       text-decoration: none;
   7       visibility: hidden;
   8     }
   9
  10     a.headerlink:hover {
  11       background-color: #c60f0f;
  12       color: white;
  13     }
  14
  15     h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, dt:hover > a.headerlink {
  16       visibility: visible;
  17     }
  18   </style><a href="index.html">Index </a>·
  19   <a href="systemd.directives.html">Directives </a>·
  20   <a href="../python-systemd/index.html">Python </a>·
  21   <a href="../libudev/index.html">libudev </a>·
  22   <a href="../libudev/index.html">gudev </a><span style="float:right">systemd 208</span><hr><div class="refentry"><a name="systemd-system.conf"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>systemd-system.conf, systemd-user.conf — System and session service manager configuration file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">/etc/systemd/system.conf</code></p><p><code class="filename">/etc/systemd/user.conf</code></p></div><div class="refsect1"><a name="idm274686659824"></a><h2 id="Description">Description<a class="headerlink" title="Permalink to this headline" href="#Description">¶</a></h2><p>When run as system instance systemd reads the
  23                 configuration file <code class="filename">system.conf</code>,
  24                 otherwise <code class="filename">user.conf</code>. These
  25                 configuration files contain a few settings controlling
  26                 basic manager operations.</p></div><div class="refsect1"><a name="idm274687554272"></a><h2 id="Options">Options<a class="headerlink" title="Permalink to this headline" href="#Options">¶</a></h2><p>All options are configured in the
  27                 "<code class="literal">[Manager]</code>" section:</p><div class="variablelist"><dl class="variablelist"><dt id="LogLevel="><span class="term"><code class="varname">LogLevel=</code>, </span><span class="term"><code class="varname">LogTarget=</code>, </span><span class="term"><code class="varname">LogColor=</code>, </span><span class="term"><code class="varname">LogLocation=</code>, </span><span class="term"><code class="varname">DumpCore=yes</code>, </span><span class="term"><code class="varname">CrashShell=no</code>, </span><span class="term"><code class="varname">ShowStatus=yes</code>, </span><span class="term"><code class="varname">CrashChVT=1</code>, </span><span class="term"><code class="varname">DefaultStandardOutput=journal</code>, </span><span class="term"><code class="varname">DefaultStandardError=inherit</code></span><a class="headerlink" title="Permalink to this term" href="#LogLevel=">¶</a></dt><dd><p>Configures various
  28                                 parameters of basic manager
  29                                 operation. These options may be
  30                                 overridden by the respective command
  31                                 line arguments. See
  32                                 <a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>
  33                                 for details about these command line
  34                                 arguments.</p></dd><dt id="CPUAffinity="><span class="term"><code class="varname">CPUAffinity=</code></span><a class="headerlink" title="Permalink to this term" href="#CPUAffinity=">¶</a></dt><dd><p>Configures the initial
  35                                 CPU affinity for the init
  36                                 process. Takes a space-separated list
  37                                 of CPU indexes.</p></dd><dt id="JoinControllers=cpu,cpuacct net_cls,netprio"><span class="term"><code class="varname">JoinControllers=cpu,cpuacct net_cls,netprio</code></span><a class="headerlink" title="Permalink to this term" href="#JoinControllers=cpu,cpuacct%20net_cls,netprio">¶</a></dt><dd><p>Configures controllers
  38                                 that shall be mounted in a single
  39                                 hierarchy. By default, systemd will
  40                                 mount all controllers which are
  41                                 enabled in the kernel in individual
  42                                 hierarchies, with the exception of
  43                                 those listed in this setting. Takes a
  44                                 space-separated list of comma-separated
  45                                 controller names, in order
  46                                 to allow multiple joined
  47                                 hierarchies. Defaults to
  48                                 'cpu,cpuacct'. Pass an empty string to
  49                                 ensure that systemd mounts all
  50                                 controllers in separate
  51                                 hierarchies.</p><p>Note that this option is only
  52                                 applied once, at very early boot. If
  53                                 you use an initial RAM disk (initrd)
  54                                 that uses systemd, it might hence be
  55                                 necessary to rebuild the initrd if
  56                                 this option is changed, and make sure
  57                                 the new configuration file is included
  58                                 in it. Otherwise, the initrd might
  59                                 mount the controller hierarchies in a
  60                                 different configuration than intended,
  61                                 and the main system cannot remount
  62                                 them anymore.</p></dd><dt id="RuntimeWatchdogSec="><span class="term"><code class="varname">RuntimeWatchdogSec=</code>, </span><span class="term"><code class="varname">ShutdownWatchdogSec=</code></span><a class="headerlink" title="Permalink to this term" href="#RuntimeWatchdogSec=">¶</a></dt><dd><p>Configure the hardware
  63                                 watchdog at runtime and at
  64                                 reboot. Takes a timeout value in
  65                                 seconds (or in other time units if
  66                                 suffixed with "<code class="literal">ms</code>",
  67                                 "<code class="literal">min</code>",
  68                                 "<code class="literal">h</code>",
  69                                 "<code class="literal">d</code>",
  70                                 "<code class="literal">w</code>"). If
  71                                 <code class="varname">RuntimeWatchdogSec=</code>
  72                                 is set to a non-zero value, the
  73                                 watchdog hardware
  74                                 (<code class="filename">/dev/watchdog</code>)
  75                                 will be programmed to automatically
  76                                 reboot the system if it is not
  77                                 contacted within the specified timeout
  78                                 interval. The system manager will
  79                                 ensure to contact it at least once in
  80                                 half the specified timeout
  81                                 interval. This feature requires a
  82                                 hardware watchdog device to be
  83                                 present, as it is commonly the case in
  84                                 embedded and server systems. Not all
  85                                 hardware watchdogs allow configuration
  86                                 of the reboot timeout, in which case
  87                                 the closest available timeout is
  88                                 picked. <code class="varname">ShutdownWatchdogSec=</code>
  89                                 may be used to configure the hardware
  90                                 watchdog when the system is asked to
  91                                 reboot. It works as a safety net to
  92                                 ensure that the reboot takes place
  93                                 even if a clean reboot attempt times
  94                                 out. By default
  95                                 <code class="varname">RuntimeWatchdogSec=</code>
  96                                 defaults to 0 (off), and
  97                                 <code class="varname">ShutdownWatchdogSec=</code>
  98                                 to 10min. These settings have no
  99                                 effect if a hardware watchdog is not
 100                                 available.</p></dd><dt id="CapabilityBoundingSet="><span class="term"><code class="varname">CapabilityBoundingSet=</code></span><a class="headerlink" title="Permalink to this term" href="#CapabilityBoundingSet=">¶</a></dt><dd><p>Controls which
 101                                 capabilities to include in the
 102                                 capability bounding set for PID 1 and
 103                                 its children. See
 104                                 <a href="capabilities.html"><span class="citerefentry"><span class="refentrytitle">capabilities</span>(7)</span></a>
 105                                 for details. Takes a whitespace-separated
 106                                 list of capability names as read by
 107                                 <a href="cap_from_name.html"><span class="citerefentry"><span class="refentrytitle">cap_from_name</span>(3)</span></a>.
 108                                 Capabilities listed will be included
 109                                 in the bounding set, all others are
 110                                 removed. If the list of capabilities
 111                                 is prefixed with ~, all but the listed
 112                                 capabilities will be included, the
 113                                 effect of the assignment
 114                                 inverted. Note that this option also
 115                                 affects the respective capabilities in
 116                                 the effective, permitted and
 117                                 inheritable capability sets. The
 118                                 capability bounding set may also be
 119                                 individually configured for units
 120                                 using the
 121                                 <code class="varname">CapabilityBoundingSet=</code>
 122                                 directive for units, but note that
 123                                 capabilities dropped for PID 1 cannot
 124                                 be regained in individual units, they
 125                                 are lost for good.</p></dd><dt id="TimerSlackNSec="><span class="term"><code class="varname">TimerSlackNSec=</code></span><a class="headerlink" title="Permalink to this term" href="#TimerSlackNSec=">¶</a></dt><dd><p>Sets the timer slack
 126                                 in nanoseconds for PID 1 which is then
 127                                 inherited to all executed processes,
 128                                 unless overridden individually, for
 129                                 example with the
 130                                 <code class="varname">TimerSlackNSec=</code>
 131                                 setting in service units (for details
 132                                 see
 133                                 <a href="systemd.exec.html"><span class="citerefentry"><span class="refentrytitle">systemd.exec</span>(5)</span></a>). The
 134                                 timer slack controls the accuracy of
 135                                 wake-ups triggered by timers. See
 136                                 <a href="prctl.html"><span class="citerefentry"><span class="refentrytitle">prctl</span>(2)</span></a>
 137                                 for more information. Note that in
 138                                 contrast to most other time span
 139                                 definitions this parameter takes an
 140                                 integer value in nano-seconds if no
 141                                 unit is specified. The usual time
 142                                 units are understood
 143                                 too.</p></dd><dt id="DefaultEnvironment="><span class="term"><code class="varname">DefaultEnvironment=</code></span><a class="headerlink" title="Permalink to this term" href="#DefaultEnvironment=">¶</a></dt><dd><p>Sets manager
 144                                 environment variables passed to all
 145                                 executed processes. Takes a
 146                                 space-separated list of variable
 147                                 assignments. See
 148                                 <a href="environ.html"><span class="citerefentry"><span class="refentrytitle">environ</span>(7)</span></a>
 149                                 for details about environment
 150                                 variables.</p><p>Example:
 151
 152                                 </p><pre class="programlisting">DefaultEnvironment="VAR1=word1 word2" VAR2=word3 "VAR3=word 5 6"</pre><p>
 153
 154                                 Sets three variables
 155                                 "<code class="literal">VAR1</code>",
 156                                 "<code class="literal">VAR2</code>",
 157                                 "<code class="literal">VAR3</code>".</p></dd><dt id="DefaultLimitCPU="><span class="term"><code class="varname">DefaultLimitCPU=</code>, </span><span class="term"><code class="varname">DefaultLimitFSIZE=</code>, </span><span class="term"><code class="varname">DefaultLimitDATA=</code>, </span><span class="term"><code class="varname">DefaultLimitSTACK=</code>, </span><span class="term"><code class="varname">DefaultLimitCORE=</code>, </span><span class="term"><code class="varname">DefaultLimitRSS=</code>, </span><span class="term"><code class="varname">DefaultLimitNOFILE=</code>, </span><span class="term"><code class="varname">DefaultLimitAS=</code>, </span><span class="term"><code class="varname">DefaultLimitNPROC=</code>, </span><span class="term"><code class="varname">DefaultLimitMEMLOCK=</code>, </span><span class="term"><code class="varname">DefaultLimitLOCKS=</code>, </span><span class="term"><code class="varname">DefaultLimitSIGPENDING=</code>, </span><span class="term"><code class="varname">DefaultLimitMSGQUEUE=</code>, </span><span class="term"><code class="varname">DefaultLimitNICE=</code>, </span><span class="term"><code class="varname">DefaultLimitRTPRIO=</code>, </span><span class="term"><code class="varname">DefaultLimitRTTIME=</code></span><a class="headerlink" title="Permalink to this term" href="#DefaultLimitCPU=">¶</a></dt><dd><p>These settings control
 158                                 various default resource limits for
 159                                 units. See
 160                                 <a href="setrlimit.html"><span class="citerefentry"><span class="refentrytitle">setrlimit</span>(2)</span></a>
 161                                 for details. Use the string
 162                                 <code class="varname">infinity</code> to
 163                                 configure no limit on a specific
 164                                 resource. These settings may be
 165                                 overridden in individual units
 166                                 using the corresponding LimitXXX=
 167                                 directives. Note that these resource
 168                                 limits are only defaults for units,
 169                                 they are not applied to PID 1
 170                                 itself.</p></dd></dl></div></div><div class="refsect1"><a name="idm274691158736"></a><h2 id="See Also">See Also<a class="headerlink" title="Permalink to this headline" href="#See%20Also">¶</a></h2><p>
 171                           <a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>,
 172                           <a href="systemd.directives.html"><span class="citerefentry"><span class="refentrytitle">systemd.directives</span>(7)</span></a>,
 173                           <a href="environ.html"><span class="citerefentry"><span class="refentrytitle">environ</span>(7)</span></a>
 174                   </p></div></div></body></html>