.\" Title: logger
.\" Author: [see the "AUTHOR(S)" section]
.\" Generator: Asciidoctor 2.0.15
-.\" Date: 2022-01-06
+.\" Date: 2022-02-17
.\" Manual: User Commands
-.\" Source: util-linux 2.37.3
+.\" Source: util-linux 2.38
.\" Language: English
.\"
-.TH "LOGGER" "1" "2022-01-06" "util\-linux 2.37.3" "User Commands"
+.TH "LOGGER" "1" "2022-02-17" "util\-linux 2.38" "User Commands"
.ie \n(.g .ds Aq \(aq
.el .ds Aq '
.ss \n[.ss] 0
.sp
\fB\-\-journald\fP[\fB=\fP\fIfile\fP]
.RS 4
-Write a systemd journal entry. The entry is read from the given \fIfile\fP, when specified, otherwise from standard input. Each line must begin with a field that is accepted by journald; see \fBsystemd.journal\-fields\fP(7) for details. The use of a MESSAGE_ID field is generally a good idea, as it makes finding entries easy. Examples:
+Write a \fBsystemd\fP journal entry. The entry is read from the given \fIfile\fP, when specified, otherwise from standard input. Each line must begin with a field that is accepted by \fBjournald\fP; see \fBsystemd.journal\-fields\fP(7) for details. The use of a MESSAGE_ID field is generally a good idea, as it makes finding entries easy. Examples:
.RE
.RS 3
.ll -.6i
.sp
\fB\-\-no\-act\fP
.RS 4
-Causes everything to be done except for writing the log message to the system log, and removing the connection or the journal. This option can be used together with \fB\-\-stderr\fP for testing purposes.
+Causes everything to be done except for writing the log message to the system log, and removing the connection to the journal. This option can be used together with \fB\-\-stderr\fP for testing purposes.
.RE
.sp
\fB\-\-octet\-count\fP
.sp
\fB\-P\fP, \fB\-\-port\fP \fIport\fP
.RS 4
-Use the specified \fIport\fP. When this option is not specified, the port defaults to syslog for udp and to syslog\-conn for tcp connections.
+Use the specified \fIport\fP. When this option is not specified, the port defaults to \fBsyslog\fP for udp and to \fBsyslog\-conn\fP for tcp connections.
.RE
.sp
\fB\-p\fP, \fB\-\-priority\fP \fIpriority\fP
.RS 4
Specifies a structured data element ID for an RFC 5424 message header. The option has to be used before \fB\-\-sd\-param\fP to introduce a new element. The number of structured data elements is unlimited. The ID (\fIname\fP plus possibly \fB@\fP\fIdigits\fP) is case\-sensitive and uniquely identifies the type and purpose of the element. The same ID must not exist more than once in a message. The \fB@\fP\fIdigits\fP part is required for user\-defined non\-standardized IDs.
.sp
-\fBlogger\fP currently generates the \fBtimeQuality\fP standardized element only. RFC 5424 also describes the elements \fBorigin\fP (with parameters ip, enterpriseId, software and swVersion) and \fBmeta\fP (with parameters sequenceId, sysUpTime and language). These element IDs may be specified without the \fB@\fP\fIdigits\fP suffix.
+\fBlogger\fP currently generates the \fBtimeQuality\fP standardized element only. RFC 5424 also describes the elements \fBorigin\fP (with parameters \fBip\fP, \fBenterpriseId\fP, \fBsoftware\fP and \fBswVersion\fP) and \fBmeta\fP (with parameters \fBsequenceId\fP, \fBsysUpTime\fP and \fBlanguage\fP). These element IDs may be specified without the \fB@\fP\fIdigits\fP suffix.
.RE
.sp
\fB\-\-sd\-param\fP \fIname\fP=\fIvalue\fP
.sp
\fB\-\-socket\-errors\fP[\fB=\fP\fImode\fP]
.RS 4
-Print errors about Unix socket connections. The \fImode\fP can be a value of \fBoff\fP, \fBon\fP, or \fBauto\fP. When the mode is \fBauto\fP, then \fBlogger\fP will detect if the init process is \fBsystemd\fP(1), and if so assumption is made \fI/dev/log\fP can be used early at boot. Other init systems lack of \fI/dev/log\fP will not cause errors that is identical with messaging using \fBopenlog\fP(3) system call. The \fBlogger\fP(1) before version 2.26 used openlog, and hence was unable to detected loss of messages sent to Unix sockets.
+Print errors about Unix socket connections. The \fImode\fP can be a value of \fBoff\fP, \fBon\fP, or \fBauto\fP. When the mode is \fBauto\fP, then \fBlogger\fP will detect if the init process is \fBsystemd\fP(1), and if so assumption is made \fI/dev/log\fP can be used early at boot. Other init systems lack of \fI/dev/log\fP will not cause errors that is identical with messaging using \fBopenlog\fP(3) system call. The \fBlogger\fP(1) before version 2.26 used \fBopenlog\fP(3), and hence was unable to detected loss of messages sent to Unix sockets.
.sp
The default mode is \fBauto\fP. When errors are not enabled lost messages are not communicated and will result to successful exit status of \fBlogger\fP(1) invocation.
.RE
End the argument list. This allows the \fImessage\fP to start with a hyphen (\-).
.RE
.sp
-\fB\-V\fP, \fB\-\-version\fP
+\fB\-h\fP, \fB\-\-help\fP
.RS 4
-Display version information and exit.
+Display help text and exit.
.RE
.sp
-\fB\-h\fP, \fB\-\-help\fP
+\fB\-V\fP, \fB\-\-version\fP
.RS 4
-Display help text and exit.
+Print version and exit.
.RE
.SH "EXIT STATUS"
.sp
.SH "REPORTING BUGS"
.sp
For bug reports, use the issue tracker at \c
-.URL "https://github.com/karelzak/util\-linux/issues" "" "."
+.URL "https://github.com/util\-linux/util\-linux/issues" "" "."
.SH "AVAILABILITY"
.sp
The \fBlogger\fP command is part of the util\-linux package which can be downloaded from \c
OSDN Git Service
