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 06/12] Manual pages: lslogins.1: Minor wording and formatting fixres
Date: Fri, 24 Jul 2020 12:06:12 +0200	[thread overview]
Message-ID: <20200724100618.584918-6-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>
---
 login-utils/lslogins.1 | 22 +++++++++++++++-------
 1 file changed, 15 insertions(+), 7 deletions(-)

diff --git a/login-utils/lslogins.1 b/login-utils/lslogins.1
index 6824001d4..0c9ea6dce 100644
--- a/login-utils/lslogins.1
+++ b/login-utils/lslogins.1
@@ -11,7 +11,10 @@ lslogins \- display information about known users in the system
 .RB [ \-l " \fIlogins\fR]"
 .RI [ username ]
 .SH DESCRIPTION
-Examine the wtmp and btmp logs, /etc/shadow (if necessary) and /etc/passwd
+Examine the wtmp and btmp logs,
+.I /etc/shadow
+(if necessary) and
+.I /passwd
 and output the desired data.
 
 The optional argument \fIusername\fR forces
@@ -46,12 +49,14 @@ Show information about supplementary groups.
 .TP
 \fB\-g\fR, \fB\-\-groups\fR=\fIgroups\fR
 Only show data of users belonging to \fIgroups\fR.  More than one group
-may be specified; the list has to be comma-separated.  The unknown group
+may be specified; the list has to be comma-separated.  Unknown group
 names are ignored.
 
 Note that relation between user and group may be invisible for primary group if
 the user is not explicitly specify as group member (e.g., in /etc/group). If the
-command lslogins scans for groups than it uses groups database only, and user
+command
+.B lslogins
+scans for groups than it uses groups database only, and user
 database with primary GID is not used at all.
 .TP
 \fB\-h\fR, \fB\-\-help\fR
@@ -63,7 +68,7 @@ Display data containing information about the users' last login sessions.
 \fB\-l\fR, \fB\-\-logins\fR=\fIlogins\fR
 Only show data of users with a login specified in \fIlogins\fR (user names or user
 IDS).  More than one login may be specified; the list has to be comma-separated.
-The unknown login names are ignored.
+Unknown login names are ignored.
 .TP
 \fB\-n\fR, \fB\-\-newline\fR
 Display each piece of information on a separate line.
@@ -94,7 +99,8 @@ Raw output (no columnation).
 Show system accounts.  These are by default all accounts with a UID between 101 and 999
 (inclusive), with the exception of either nobody or nfsnobody (UID 65534).
 This hardcoded default may be overwritten by parameters SYS_UID_MIN and SYS_UID_MAX in
-the file /etc/login.defs.
+the file
+.IR /etc/login.defs .
 .TP
 \fB\-\-time\-format\fR \fItype\fP
 Display dates in short, full or iso format.  The default is short, this time
@@ -104,7 +110,8 @@ format is designed to be space efficient and human readable.
 Show user accounts.  These are by default all accounts with UID above 1000
 (inclusive), with the exception of either nobody or nfsnobody (UID 65534).
 This hardcoded default maybe overwritten by parameters UID_MIN and UID_MAX in
-the file /etc/login.defs.
+the file
+.IR /etc/login.defs .
 .TP
 \fB\-V\fR, \fB\-\-version\fR
 Display version information and exit.
@@ -132,7 +139,8 @@ if incorrect arguments specified,
 2
 if a serious error occurs (e.g., a corrupt log).
 .SH NOTES
-The default UID thresholds are read from /etc/login.defs.
+The default UID thresholds are read from
+.IR /etc/login.defs .
 
 .SH HISTORY
 The \fBlslogins\fP utility is inspired by the \fBlogins\fP utility, which first appeared in FreeBSD 4.10.
-- 
2.26.2


  parent reply	other threads:[~2020-07-24 10:06 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 ` Michael Kerrisk (man-pages) [this message]
2020-07-24 10:06 ` [PATCH 07/12] Manual pages: nologin.8: formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 08/12] Manual pages: logger.1: minor formatting and typo fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 09/12] Manual pages: lsblk.8: Minor " 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-6-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).