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 1/5] Manual pages: kill.1: various language, spelling, and formatting fixes
Date: Mon, 25 May 2020 14:59:08 +0200 [thread overview]
Message-ID: <20200525125912.43748-1-mtk.manpages@gmail.com> (raw)
These seem all "obviously correct", so I'm rolling them up into
one patch.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
---
misc-utils/kill.1 | 25 ++++++++++++++++---------
1 file changed, 16 insertions(+), 9 deletions(-)
diff --git a/misc-utils/kill.1 b/misc-utils/kill.1
index 6fd50036d..1c12f8a14 100644
--- a/misc-utils/kill.1
+++ b/misc-utils/kill.1
@@ -34,7 +34,9 @@ then the KILL signal may be used; be aware that the latter signal
cannot be caught, and so does not give the target process the opportunity
to perform any clean-up before terminating.
.PP
-Most modern shells have a builtin kill command, with a usage rather similar to
+Most modern shells have a builtin
+.B kill
+command, with a usage rather similar to
that of the command described here. The
.BR \-\-all ,
.BR \-\-pid ", and"
@@ -49,7 +51,7 @@ The list of processes to be signaled can be a mixture of names and PIDs.
.I pid
Each
.I pid
-can be one of four things:
+can be expressed in one of the following ways:
.RS
.TP
.I n
@@ -87,7 +89,7 @@ The signal to send. It may be given as a name or a number.
\fB\-l\fR, \fB\-\-list\fR [\fInumber\fR]
Print a list of signal names, or convert the given signal number to a name.
The signals can be found in
-.I /usr/\:include/\:linux/\:signal.h
+.IR /usr/\:include/\:linux/\:signal.h .
.TP
\fB\-L\fR, \fB\-\-table\fR
Similar to \fB\-l\fR, but it will print signal names and their corresponding
@@ -102,10 +104,12 @@ Only print the process ID (PID) of the named processes, do not send any
signals.
.TP
\fB\-\-verbose\fR
-Print PID(s) that will be signaled with kill along with the signal.
+Print PID(s) that will be signaled with
+.B kill
+along with the signal.
.TP
\fB\-q\fR, \fB\-\-queue\fR \fIvalue\fR
-Use
+Send the signal using
.BR sigqueue (3)
rather than
.BR kill (2).
@@ -132,7 +136,7 @@ to wait for a period defined in
before sending follow-up
.I signal
to process.
-This feature is implemented by PID file-descriptor and guaranties that
+This feature is implemented by PID file-descriptor and guarantees that
follow-up signals are sent to the same process or not sent if the process no
more exist. Note that the operating system may re-use PIDs and implement the
same feature in a shell by kill and sleep commands sequence may introduce a
@@ -182,11 +186,14 @@ and the description of
in
.BR clone (2).
.P
-Various shells have provide an internal kill implementation that is
+Various shells provide a builtin
+.B kill
+command that is
preferred in relation to the
.BR kill (1)
-executable described by this manual. Easiest way to ensure one is executing
-the executable is to use full path when calling the command, for example:
+executable described by this manual.
+The easiest way to ensure one is executing the command described in this page
+is to use the full path when calling the command, for example:
.B "/bin/kill \-\-version"
.SH AUTHORS
.MT svalente@mit.edu
--
2.26.2
next reply other threads:[~2020-05-25 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 12:59 Michael Kerrisk (man-pages) [this message]
2020-05-25 12:59 ` [PATCH 2/5] Manual pages: kill.1: improve the description of the --timout option Michael Kerrisk (man-pages)
2020-05-25 12:59 ` [PATCH 3/5] Manual pages: ipcmk.1, ipcrm.1, ipcs.1, lsipc.1: SEE ALSO: add sysvipc(7) Michael Kerrisk (man-pages)
2020-05-25 12:59 ` [PATCH 4/5] Man pages: ipcmk.1, ipcs.1, lsipc.1: explicitly mention "System V" Michael Kerrisk (man-pages)
2020-05-25 12:59 ` [PATCH 5/5] Manual pages: rename EXAMPLE section to EXAMPLES Michael Kerrisk (man-pages)
2020-05-28 12:53 ` [PATCH 1/5] Manual pages: kill.1: various language, spelling, and formatting fixes 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=20200525125912.43748-1-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).