+
+ <varlistentry>
+ <term><option>--realize[=MODE]</option></term>
+
+ <listitem><para>After
+ enabling/disabling stop/restart/stop
+ the unit and reload manager
+ configuration. Optionally, takes one
+ of <option>no</option>,
+ <option>reload</option>,
+ <option>minimal</option>,
+ <option>maybe</option> or
+ <option>yes</option>. If
+ <option>no</option> is passed the
+ manager will not reload its
+ configuration and no service will be
+ started or stopped after
+ enabling/disabling of the unit
+ files. If <option>reload</option> is
+ passed the daemon configuration is
+ reloaded but the unit otherwise not
+ started/stopped/restarted. If
+ <option>minimal</option> is passed and
+ a unit is being enabled it will also
+ be restarted should it already be
+ running. If a unit is being disabled
+ it will be stopped should it be
+ running. In either case the daemon
+ configuration is
+ reloaded. <option>maybe</option> is
+ similar to this, but the unit will
+ also be started if it is being enabled
+ and any of the units listed in
+ <varname>WantedBy=</varname> in the
+ <literal>[Install]</literal> section
+ of the unit file is already
+ activated. Finally
+ <option>yes</option> starts the unit
+ unconditionally after enabling. This
+ setting defaults to
+ <option>no</option>. If
+ <option>--realize</option> is
+ specifieed but the mode value is
+ omitted defaults to
+ <option>maybe</option>. This option
+ has no effect when
+ <option>--global</option> or
+ <command>test</command> is used, or
+ when systemd is not running or the
+ command is executed in a
+ <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>2</manvolnum></citerefentry>
+ environment. This option is implied if
+ the <command>realize</command> command
+ is used.</para></listitem>
+ </varlistentry>