From: Ondrej Oprala <ooprala@redhat.com>
To: util-linux@vger.kernel.org
Subject: [PATCH 06/10] nologin: minor man page improvements
Date: Tue, 8 Apr 2014 09:48:45 +0200 [thread overview]
Message-ID: <1396943329-22347-7-git-send-email-ooprala@redhat.com> (raw)
In-Reply-To: <1396943329-22347-1-git-send-email-ooprala@redhat.com>
Signed-off-by: Ondrej Oprala <ooprala@redhat.com>
---
login-utils/nologin.8 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/login-utils/nologin.8 b/login-utils/nologin.8
index f91029d..269daf5 100644
--- a/login-utils/nologin.8
+++ b/login-utils/nologin.8
@@ -9,7 +9,7 @@ nologin \- politely refuse a login
.SH DESCRIPTION
.B nologin
displays a message that an account is not available and exits non-zero. It is
-intended as a replacement shell field to deny login access to account.
+intended as a replacement shell field to deny login access to an account.
.PP
If the file /etc/nologin.txt exists, nologin displays its contents to the
user instead of the default message.
@@ -25,15 +25,15 @@ Display help text and exit.
Display version information and exit.
.SH NOTES
.B nologin
-is per-account way to disable login (usually used for system accounts like http or ftp).
+is a per-account way to disable login (usually used for system accounts like http or ftp).
.BR nologin (8)
-uses /etc/nologin.txt as optional source for non-default message, the login
-access is always refused independently on the file.
+uses /etc/nologin.txt as an optional source for a non-default message, the login
+access is always refused independently of the file.
.PP
.BR pam_nologin (8)
PAM module usually prevents all non-root users from logging into the system.
.BR pam_nologin (8)
-functionality is controlled by /var/run/nologin or /etc/nologin file.
+functionality is controlled by /var/run/nologin or the /etc/nologin file.
.SH AUTHORS
.UR kzak@redhat.com
Karel Zak
--
1.8.5.1
next prev parent reply other threads:[~2014-04-08 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 7:48 [PATCH 00/10] Man page corrections v1.0 Ondrej Oprala
2014-04-08 7:48 ` [PATCH 01/10] last: fix minor typos in the man page Ondrej Oprala
2014-04-08 7:48 ` [PATCH 02/10] runuser: " Ondrej Oprala
2014-04-08 7:48 ` [PATCH 03/10] su: " Ondrej Oprala
2014-04-08 7:48 ` [PATCH 04/10] sulogin: minor man page improvements Ondrej Oprala
2014-04-08 7:48 ` [PATCH 05/10] utmpdump: " Ondrej Oprala
2014-04-08 7:48 ` Ondrej Oprala [this message]
2014-04-08 7:48 ` [PATCH 07/10] vipw: " Ondrej Oprala
2014-04-08 7:48 ` [PATCH 08/10] addpart: " Ondrej Oprala
2014-04-08 7:48 ` [PATCH 09/10] cfdisk: " Ondrej Oprala
2014-04-08 7:48 ` [PATCH 10/10] delpart: " Ondrej Oprala
2014-04-14 11:46 ` [PATCH 00/10] Man page corrections v1.0 Karel Zak
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=1396943329-22347-7-git-send-email-ooprala@redhat.com \
--to=ooprala@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