util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: mtk.manpages@gmail.com, Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: [PATCH 08/12] Manual pages: logger.1: minor formatting and typo fixes
Date: Fri, 24 Jul 2020 12:06:14 +0200	[thread overview]
Message-ID: <20200724100618.584918-8-mtk.manpages@gmail.com> (raw)
In-Reply-To: <20200724100618.584918-1-mtk.manpages@gmail.com>

Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
---
 misc-utils/logger.1 | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/misc-utils/logger.1 b/misc-utils/logger.1
index 448311d03..f9c2b6b9e 100644
--- a/misc-utils/logger.1
+++ b/misc-utils/logger.1
@@ -49,8 +49,10 @@ given either, then standard input is logged.
 .TP
 .BR \-d , " \-\-udp"
 Use datagrams (UDP) only.  By default the connection is tried to the
-syslog port defined in /etc/services, which is often 514 .
-.sp
+syslog port defined in
+.IR /etc/services ,
+which is often 514.
+.IP
 See also \fB\-\-server\fR and \fB\-\-socket\fR to specify where to connect.
 .TP
 .BR \-e , " \-\-skip-empty"
@@ -75,7 +77,9 @@ command's PID.  The use of \fB\-\-id=$$\fR
 (PPID) is recommended in scripts that send several messages.
 
 Note that the system logging infrastructure (for example \fBsystemd\fR when
-listening on /dev/log) may follow local socket credentials to overwrite the
+listening on
+.IR /dev/log )
+may follow local socket credentials to overwrite the
 PID specified in the message.
 .BR logger (1)
 is able to set those socket credentials to the given \fIid\fR, but only if you
-- 
2.26.2


  parent reply	other threads:[~2020-07-24 10:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 10:06 [PATCH 01/12] Manual pages: blockdev.8: Minor wording and formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 02/12] Manual pages: fsck.cramfs.8: Wording fix Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 03/12] Manual pages: raw.8: Minor formatting and wording fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 04/12] Manual pages: sfdisk.8: Minor wording and formatting fixes Michael Kerrisk (man-pages)
2020-07-24 16:32   ` Nuno Silva
2020-08-27 15:16     ` Michael Kerrisk
2020-08-28 11:09       ` Nuno Silva
2020-07-24 10:06 ` [PATCH 05/12] Manual pages: sfdisk.8: Use less aggressive indenting Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 06/12] Manual pages: lslogins.1: Minor wording and formatting fixres Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 07/12] Manual pages: nologin.8: formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` Michael Kerrisk (man-pages) [this message]
2020-07-24 10:06 ` [PATCH 09/12] Manual pages: lsblk.8: Minor formatting and typo fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 10/12] Manual pages: wdctl.8: typo fix Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 11/12] Manual pages: agetty.8: Minor formatting and wording fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 12/12] Manual pages: wipefs.8: Formatting fixes Michael Kerrisk (man-pages)
2020-07-24 12:43 ` [PATCH 01/12] Manual pages: blockdev.8: Minor wording and formatting fixes Karel Zak
2020-07-24 16:07 ` Nuno Silva

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200724100618.584918-8-mtk.manpages@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).