[Pkg-sysvinit-devel] Bug#890478: pidof.8: Some corrections to the manual

Bjarni Ingi Gislason bjarniig at rhi.hi.is
Thu Feb 15 01:16:58 UTC 2018


Package: sysvinit-utils
Version: 2.88dsf-59.10
Severity: minor
Tags: patch

Dear Maintainer,

Test nr. 17: Start an empty line with ".sp 1".

84:

#####

Test nr. 25: Find a repeated word

! 56 --> the
! 81 --> that	fixes bug #815 839 from 24 February 2016

#####

Test nr. 27: Wrong distance between sentences or protect the indicator.

1) Separate the sentences; each begins on a new line.
See man-pages(7) and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.
The "indicator" is an "end-of-sentence character" (.!?).

35:finds the process id's (pids) of the named programs. It prints those
36:id's on the standard output. This program is on some systems used in
38:\fISystem-V\fP like \fIrc\fP structure. In that case these scripts are
39:located in /etc/rc?.d, where ? is the runlevel. If the system has
63:Tells \fIpidof\fP to omit processes with that process id. The special
78:should find the pid of, it is reasonably safe. Otherwise it is possible
80:as the program you're after but are actually other programs. Note that

#####

  NO PATCH IS PROVIDED FOR THIS

Test nr. 29: Surround a block of comments with the macros ".ig" and "..".
The .\" at the beginning of each line is then not needed.

  Lines 2-17

#####

Test nr. 33: Three periods for an ellipsis

28:.IR omitpid[,omitpid..] ]
30:.IR omitpid[,omitpid..].. ]
32:.RB [ program.. ]

#####

  The patch:

--- pidof.8	2017-09-08 19:18:37.000000000 +0000
+++ pidof.8.new	2018-02-15 00:39:48.000000000 +0000
@@ -25,19 +25,19 @@ pidof -- find the process ID of a runnin
 .RB [ \-n ]
 .RB [ \-x ]
 .RB [ \-o
-.IR omitpid[,omitpid..] ]
-.RB [ \-o
-.IR omitpid[,omitpid..].. ]
+.IR omitpid [, omitpid "...] ]"
 .B program
-.RB [ program.. ]
+.RB [ program ...]
 .SH DESCRIPTION
 .B Pidof
-finds the process id's (pids) of the named programs. It prints those
-id's on the standard output. This program is on some systems used in
-run-level change scripts, especially when the system has a
-\fISystem-V\fP like \fIrc\fP structure. In that case these scripts are
-located in /etc/rc?.d, where ? is the runlevel. If the system has
-a
+finds the process id's (pids) of the named programs.
+It prints those id's on the standard output.
+This program is on some systems used in run-level change scripts,
+especially when the system has a \fISystem-V\fP like \fIrc\fP
+structure.
+In that case these scripts are located in /etc/rc?.d,
+where ? is the runlevel.
+If the system has a
 .B start-stop-daemon
 (8) program that should be used instead.
 .SH OPTIONS
@@ -53,16 +53,17 @@ Avoid
 system function call on all binaries which are located on network
 based file systems like
 .BR NFS .
-Instead of using this option the the variable
+Instead of using this option the variable
 .B PIDOF_NETFS
 may be set and exported.
 .IP \-x
 Scripts too - this causes the program to also return process id's of
 shells running the named scripts.
 .IP "-o \fIomitpid\fP"
-Tells \fIpidof\fP to omit processes with that process id. The special
-pid \fB%PPID\fP can be used to name the parent process of the \fIpidof\fP
-program, in other words the calling shell or shell script.
+Tells \fIpidof\fP to omit processes with that process id.
+The special pid \fB%PPID\fP can be used to name the parent process of
+the \fIpidof\fP program,
+in other words the calling shell or shell script.
 .SH "EXIT STATUS"
 .TP
 .B 0
@@ -75,13 +76,14 @@ No program was found with the requested
 the program behaves according to the name under which it is called.
 .PP
 When \fIpidof\fP is invoked with a full pathname to the program it
-should find the pid of, it is reasonably safe. Otherwise it is possible
-that it returns pids of running programs that happen to have the same name
-as the program you're after but are actually other programs. Note that
-that the executable name of running processes is calculated with
+should find the pid of, it is reasonably safe.
+Otherwise it is possible that it returns pids of running programs that
+happen to have the same name as the program you're after but are
+actually other programs.
+Note that the executable name of running processes is calculated with
 .BR readlink (2),
 so symbolic links to executables will also match.
-
+.sp 1
 .SH SEE ALSO
 .BR shutdown (8),
 .BR init (8),

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.80-2 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sysvinit-utils depends on:
ii  init-system-helpers  1.51
ii  libc6                2.26-6
ii  util-linux           2.30.2-0.3

sysvinit-utils recommends no packages.

sysvinit-utils suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason



More information about the Pkg-sysvinit-devel mailing list