aboutsummaryrefslogtreecommitdiff
path: root/src/genrc.8
diff options
context:
space:
mode:
authorSergey Poznyakoff <gray@gnu.org.ua>2019-09-13 09:34:47 +0300
committerSergey Poznyakoff <gray@gnu.org.ua>2019-09-13 09:34:47 +0300
commit680f6e14bfdebb226fa8420903384f70f5b98459 (patch)
tree76144b69aa63f0dda95648800dfc8fdcb5514b4f /src/genrc.8
parent4f60d13820ad95d876f6daacefe4e72ffff57a5f (diff)
downloadgenrc-680f6e14bfdebb226fa8420903384f70f5b98459.tar.gz
genrc-680f6e14bfdebb226fa8420903384f70f5b98459.tar.bz2
Minor fixes in the manpage
Diffstat (limited to 'src/genrc.8')
-rw-r--r--src/genrc.836
1 files changed, 18 insertions, 18 deletions
diff --git a/src/genrc.8 b/src/genrc.8
index ed077bf..0fdfa54 100644
--- a/src/genrc.8
+++ b/src/genrc.8
@@ -15,3 +15,3 @@
.\" along with genrc. If not, see <http://www.gnu.org/licenses/>.
-.TH GENRC 8 "July 11, 2019" "GENRC" "Genrc User Manual"
+.TH GENRC 8 "September 13, 2019" "GENRC" "Genrc User Manual"
.SH NAME
@@ -88,3 +88,3 @@ The program operation modes are:
.SS start
-If given \fBstart\fR argument, \fBgenrc\fR runs the supplier
+If given this argument, \fBgenrc\fR runs the supplied
command. Before, it checks if the program is not already running and
@@ -93,6 +93,6 @@ refuses to start its second copy if so.
It is supposed that the program to be run will detach from the
-controlling terminal and continue running in the background (i.e. it
+controlling terminal and will continue running in the background (i.e. it
is a \fIdaemon\fR, in UNIX sense). If it is not the case, use the
\fB\-\-sentinel\fR option. With this option, \fBgenrc\fR will start
-the command and will become daemon itself, controlling the execution
+the command and become a daemon itself, controlling the execution
of the program. It will exit when the command terminates. So long as
@@ -115,4 +115,4 @@ service provided by the program won't get terminated because of
hitting a bug or encountering an unforeseen external condition. For
-example, the following two options will ensure that the program will
-be terminated only if it exits with status 0 or it is terminated by
+example, the following two options make sure that the program will
+be terminated only if it exits with status 0 or is delivered the
SIGTERM or SIGQUIT signal:
@@ -136,3 +136,3 @@ already running and outputs its status on the standard output. To this
effect, it uses an abstraction called \fIPID source\fR, which allows
-it to determine the PID of the program by its name of command line.
+it to determine the PID of the program.
.PP
@@ -140,3 +140,3 @@ The default PID source is the Linux \fB/proc\fR filesystem (or, if it
is not available, the output of \fBps -ef\fR), which is scanned for
-the name of the program (given by \fB\-\-program\fR or
+the name of the program (as given by \fB\-\-program\fR or
\fB\-\-command\fR options).
@@ -144,3 +144,3 @@ the name of the program (given by \fB\-\-program\fR or
The source to use can be supplied with the \fB\-\-pid\-from\fR option
-(or the \fB\-\-pidfile option, which is equivalent to
+(or the \fB\-\-pidfile\R option, which is equivalent to
\fB\-\-pid\-from=FILE:\fR). See the section \fBPID SOURCES\fR for a
@@ -149,3 +149,3 @@ detailed discussion of available sources.
In the \fBstop\fR mode \fBgenrc\fR stops the command by sending it
-\fBSIGTERM\fR (or another signal as supplied with the
+\fBSIGTERM\fR (or another signal, as supplied with the
\fB\-\-signal\-stop\fR option). If the PID source returns multiple
@@ -156,3 +156,3 @@ description of \fBPROC\fR or \fBPS\fR PID source).
After sending the signal, the program will wait for all processes to
-terminate. It will report error if they don't terminate within 5
+terminate. It will report an error if they don't terminate within 5
seconds. This timeout can be changed using the \fB\-\-timeout\fR
@@ -165,3 +165,3 @@ immediately followed by
.SS reload
-Attempt to reload (or reconfigure) the program by sending it the
+Attempts to reload (or reconfigure) the program by sending it the
\fBSIGHUP\fR signal (or another signal, as given with the
@@ -210,3 +210,3 @@ rest of them supplementary groups. Each \fIGROUP\fR is either a group
name or a numeric group number prefixed with a plus sign. Whatever
-notation is used, it must exist in the system group database.
+notation is used, the groups must exist in the system group database.
@@ -324,4 +324,4 @@ Configuration specified as fully-qualified keyword-value pairs
\fBGREP:\fIFILE\fB:s/\fIRX\fB/\fIREPL\fB/[\fIFLAGS\fR][\fB;\fR...]
-Grep for the first line in \fIFILE\fR that matches \fIRX\fR. If found, process
-replace the matched portion according to \fIREPL\fR and \fIFLAGS\fR. Use
+Grep for the first line in \fIFILE\fR that matches \fIRX\fR. If found,
+modify the matched portion according to \fIREPL\fR and \fIFLAGS\fR. Use
the resulting string as PID. More sed expressions can be supplied,
@@ -331,3 +331,3 @@ separated with semicolons.
Look for matching program in \fB/proc/\fIPID\fB/*\fR. If \fIEXE\fR is
-not supplied or empty, program name from \fB\-\-program\fR will be
+not supplied or empty, the program name from \fB\-\-program\fR will be
used. \fIFLAGS\fR are:
@@ -360,3 +360,3 @@ signal all matching PIDs
.TP
-\fBPS:\fR[\fB:\fR[\fIEXE\fR][:\fIFLAGS\fR]]
+\fBPS\fR[\fB:\fR[\fIEXE\fR][:\fIFLAGS\fR]]
Look for matching program in the output of \fBps \-ef\fR. \fIEXE\fR
@@ -384,3 +384,3 @@ Report bugs to <gray@gnu.org>.
.SH COPYRIGHT
-Copyright \(co 2018 Sergey Poznyakoff
+Copyright \(co 2018, 2019 Sergey Poznyakoff
.br

Return to:

Send suggestions and report system problems to the System administrator.