diff options
| author | Mathieu Tortuyaux <mtortuyaux@microsoft.com> | 2023-04-25 14:06:59 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2023-08-21 11:13:54 +0200 |
| commit | 41712cd1c0d774d5eac592964f25d798df44a190 (patch) | |
| tree | 92dea9b9316b744beb2da1ebf33571b46431ca2d /man/systemd-sysext.xml | |
| parent | generators: use generator_open_unit_file where appropriate (diff) | |
| download | systemd-41712cd1c0d774d5eac592964f25d798df44a190.tar.xz systemd-41712cd1c0d774d5eac592964f25d798df44a190.zip | |
sysext: support EXTENSION_RELOAD_MANAGER metadata
This metadata (EXTENSION_RELOAD_MANAGER) can be set to "1" to reload the manager
when merging/refreshing/unmerging a system extension image. This can be useful in case the sysext
image provides systemd units that need to be loaded.
With `--no-reload`, one can deactivate the EXTENSION_RELOAD_MANAGER metadata interpretation.
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Diffstat (limited to 'man/systemd-sysext.xml')
| -rw-r--r-- | man/systemd-sysext.xml | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/man/systemd-sysext.xml b/man/systemd-sysext.xml index db6b223555..08540feab2 100644 --- a/man/systemd-sysext.xml +++ b/man/systemd-sysext.xml @@ -139,6 +139,11 @@ architecture reported by <citerefentry><refentrytitle>uname</refentrytitle><manvolnum>2</manvolnum></citerefentry> but the used architecture identifiers are the same as for <varname>ConditionArchitecture=</varname> described in <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. + <varname>EXTENSION_RELOAD_MANAGER=</varname> can be set to 1 if the extension requires a service manager reload after application + of the extension. Note that the for the reasons mentioned earlier: + <ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink> remain + the recommended way to ship system services. + System extensions should not ship a <filename>/usr/lib/os-release</filename> file (as that would be merged into the host <filename>/usr/</filename> tree, overriding the host OS version data, which is not desirable). The <filename>extension-release</filename> file follows the same format and semantics, and carries the same @@ -299,6 +304,17 @@ it.</para></listitem> </varlistentry> + <varlistentry> + <term><option>--no-reload</option></term> + + <listitem> + <para>When used with <command>merge</command>, + <command>unmerge</command> or <command>refresh</command>, do not reload daemon + after executing the changes even if an extension that is applied requires a reload via the + <varname>EXTENSION_RELOAD_MANAGER=</varname> set to 1.</para> + </listitem> + </varlistentry> + <xi:include href="standard-options.xml" xpointer="no-pager" /> <xi:include href="standard-options.xml" xpointer="no-legend" /> <xi:include href="standard-options.xml" xpointer="json" /> |