From 9298304cb29cf11e006ac9b7785277b3736fe063 Mon Sep 17 00:00:00 2001 From: Alexey Gladkov Date: Thu, 14 May 2020 16:02:11 +0300 Subject: ALT: Drop documentation about --journald option since we compile logger without systemd support Signed-off-by: Alexey Gladkov --- misc-utils/logger.1.adoc | 22 +--------------------- 1 file changed, 1 insertion(+), 21 deletions(-) diff --git a/misc-utils/logger.1.adoc b/misc-utils/logger.1.adoc index 7037fcb09..857d35f26 100644 --- a/misc-utils/logger.1.adoc +++ b/misc-utils/logger.1.adoc @@ -75,24 +75,6 @@ Log the PID of the *logger* process with each line. When the optional argument _ + Note that the system logging infrastructure (for example *systemd* when listening on _/dev/log_) may follow local socket credentials to overwrite the PID specified in the message. *logger*(1) is able to set those socket credentials to the given _id_, but only if you have root permissions and a process with the specified PID exists, otherwise the socket credentials are not modified and the problem is silently ignored. -*--journald*[**=**__file__]:: -Write a *systemd* journal entry. The entry is read from the given _file_, when specified, otherwise from standard input. Each line must begin with a field that is accepted by *journald*; see *systemd.journal-fields*(7) for details. The use of a MESSAGE_ID field is generally a good idea, as it makes finding entries easy. Examples: -+ -____ - logger --journald <