From: Lennart Poettering <lennart@poettering.net>
Date: Wed, 20 Jan 2021 21:27:41 +0000 (+0100)
Subject: man: document how get logging to work in a RootDirectory=/RootImage= environment
X-Git-Tag: v248-rc1~283^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=09872a6e1a88d68013653d7299df96d5e542bfe6;p=thirdparty%2Fsystemd.git

man: document how get logging to work in a RootDirectory=/RootImage= environment

Fixes: #18051
---

diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml
index 663b15fa601..8f00ef555e0 100644
--- a/man/systemd.exec.xml
+++ b/man/systemd.exec.xml
@@ -117,6 +117,20 @@
         <para>The <varname>MountAPIVFS=</varname> and <varname>PrivateUsers=</varname> settings are particularly useful
         in conjunction with <varname>RootDirectory=</varname>. For details, see below.</para>
 
+        <para>If <varname>RootDirectory=</varname>/<varname>RootImage=</varname> are used together with
+        <varname>NotifyAccess=</varname> the notification socket is automatically mounted from the host into
+        the root environment, to ensure the notification interface can work correctly.</para>
+
+        <para>Note that services using <varname>RootDirectory=</varname>/<varname>RootImage=</varname> will
+        not be able to log via the syslog or journal protocols to the host logging infrastructure, unless the
+        relevant sockets are mounted from the host, specifically:</para>
+
+        <example>
+          <title>Mounting logging sockets into root environment</title>
+
+          <programlisting>BindReadOnlyPaths=/dev/log /run/systemd/journal/socket /run/systemd/journal/stdout</programlisting>
+        </example>
+
         <xi:include href="system-only.xml" xpointer="singular"/></listitem>
       </varlistentry>