man: mention that stdout logging works the same as stderr logging

Apparently people wondered about that:

https://lists.freedesktop.org/archives/systemd-devel/2020-March/044091.html

diff --git a/man/sd-daemon.xml b/man/sd-daemon.xml
index 84deda188d22fa17d7a738a44e1ab3690693c409..64ed5f3779c73ac71a87d7b4a552b88f13e4b62f 100644 (file)
--- a/man/sd-daemon.xml
+++ b/man/sd-daemon.xml
@@ -68,16 +68,14 @@
 #define SD_INFO    "<6>"  /* informational */
 #define SD_DEBUG   "&lt;7&gt;"  /* debug-level messages */</programlisting>
 
-    <para>These prefixes are intended to be used in conjunction with
-    stderr-based logging as implemented by systemd. If a systemd
-    service definition file is configured with
-    <varname>StandardError=journal</varname>,
-    <varname>StandardError=syslog</varname> or
-    <varname>StandardError=kmsg</varname>, these prefixes can be used
-    to encode a log level in lines printed. This is similar to the
-    kernel <function>printk()</function>-style logging. See
-    <citerefentry><refentrytitle>klogctl</refentrytitle><manvolnum>2</manvolnum></citerefentry>
-    for more information.</para>
+    <para>These prefixes are intended to be used in conjunction with stderr-based logging (or stdout-based
+    logging) as implemented by systemd. If a systemd service definition file is configured with
+    <varname>StandardError=journal</varname>, <varname>StandardError=syslog</varname> or
+    <varname>StandardError=kmsg</varname> (and similar with <varname>StandardOutput=</varname>), these
+    prefixes can be used to encode a log level in lines printed. This is similar to the kernel
+    <function>printk()</function>-style logging. See
+    <citerefentry><refentrytitle>klogctl</refentrytitle><manvolnum>2</manvolnum></citerefentry> for more
+    information.</para>
 
     <para>The log levels are identical to
     <citerefentry project='man-pages'><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>'s