From 9e76a88fafcba7d5bd7736013b6cb2eb291a006f Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 31 Mar 2020 15:59:29 +0200 Subject: 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 --- man/sd-daemon.xml | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) (limited to 'man/sd-daemon.xml') diff --git a/man/sd-daemon.xml b/man/sd-daemon.xml index 84deda188d..64ed5f3779 100644 --- a/man/sd-daemon.xml +++ b/man/sd-daemon.xml @@ -68,16 +68,14 @@ #define SD_INFO "<6>" /* informational */ #define SD_DEBUG "<7>" /* debug-level messages */ - 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 - StandardError=journal, - StandardError=syslog or - StandardError=kmsg, these prefixes can be used - to encode a log level in lines printed. This is similar to the - kernel printk()-style logging. See - klogctl2 - for more information. + 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 + StandardError=journal, StandardError=syslog or + StandardError=kmsg (and similar with StandardOutput=), these + prefixes can be used to encode a log level in lines printed. This is similar to the kernel + printk()-style logging. See + klogctl2 for more + information. The log levels are identical to syslog3's -- cgit v1.2.1