Package: liblockfile-bin Version: 1.14-1.1 Severity: minor Tags: patch Dear Maintainer,
* What led up to the situation? Warnings from "groff": <dotlockfile.1>:6 (macro RB): only 1 argument, but more are expected <dotlockfile.1>:13 (macro RB): only 1 argument, but more are expected Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z ["test-groff" is a developmental version of "groff"] ### Changes: Use the correct macro for the font change of one argument. Separate an ellipsis from the preceding string with a space character, if it does not mean a continuation of it. See a manual of style about the difference between "abc..." and "abc ...". Change - to \- if it means a minus sign. Begin a sentence on a new line. Use \(en for a dash (en-dash) between space characters. Fix some spelling mistakes. Change the font of some words. ### More details: Input file is dotlockfile.1 Test nr. 16: Use the correct macro for the font change of one argument. Split a punctuation mark from the only argument if one is there 6:.RB \-l 13:.RB \-l #### Test nr. 10: Separate an ellipsis from the preceding string with a space character, if it does not mean a continuation of it. See a manual of style about the difference between "abc..." and "abc ...". 18:.IR cmd \ args... 115:.IP "command arguments..." ##### Test nr. 18: Change - to \- if it means a minus sign. 82:To try indefinitely, use "\fB\-r -1\fR". ##### Test nr. 41: Wrong distance between sentences or protect the indicator. 1) Separate the sentences and subordinate clauses; each begins on a new line. See man-pages(7) [package "manpages"] 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" (.!?). 128:of the command that was run. If the locking and unlocking was succesful, ##### Input file is dotlockfile.1 Test nr. 44: Use \(en for a dash (en-dash) between space characters, not a minus (\-), except in the NAME section. 56:were already taken \- hence the name \fBdotlockfile\fR \fI:)\fR. ##### Patch: --- dotlockfile.1 2018-05-23 03:35:12.000000000 +0000 +++ dotlockfile.1.new 2018-05-23 04:41:40.000000000 +0000 @@ -1,21 +1,23 @@ -.TH DOTLOCKFILE 1 "Januari 10, 2017" "" "Cistron Utilities" +.TH DOTLOCKFILE 1 "January 10, 2017" "" "Cistron Utilities" .SH NAME dotlockfile \- Utility to manage lockfiles .SH SYNOPSIS .B dotlockfile -.RB \-l +.B \-l .RB [ \-r .IR retries ] .RB [ \-p ] -.RB < \-m \ | \ lockfile > +.RB < \-m \ | +.IR lockfile > .br .B dotlockfile -.RB \-l +.B \-l .RB [ \-r .IR retries ] .RB [ \-p ] -.RB < \-m \ | \ lockfile > -.IR cmd \ args... +.RB < \-m \ | +.IR lockfile > +.IR cmd "\ args \&...\&" .br .B dotlockfile .RB \-u \ | \ \-t @@ -53,7 +55,7 @@ The names .B dotlock and .B lockfile -were already taken \- hence the name \fBdotlockfile\fR \fI:)\fR. +were already taken \(en hence the name \fBdotlockfile\fR \fI:)\fR. .SH OPTIONS .IP "\fB\-l\fR" Create a lockfile if no preexisting valid lockfile is found, else wait and retry @@ -75,11 +77,11 @@ The number of times .B dotlockfile retries to acquire the lock if it failed the first time before giving up. The initial sleep after failing to acquire the lock is 5\ seconds. -After each retry the sleep intervall is increased incrementally by 5\ seconds +After each retry the sleep interval is increased incrementally by 5\ seconds up to a maximum sleep of 60\ seconds between tries. The default number of retries is 5. To try only once, use "\fB\-r 0\fR". -To try indefinitely, use "\fB\-r -1\fR". +To try indefinitely, use "\fB\-r \-1\fR". .IP "\fB\-u\fR" Remove a lockfile. .IP "\fB\-t\fR" @@ -112,7 +114,7 @@ lockfile. .IP lockfile The lockfile to be created or removed. Must not be specified if the \fB\-m\fR option is given. -.IP "command arguments..." +.IP "\fIcommand\fR argument \&...\&" Create lockfile, run the .I command , wait for it to exit, and remove lockfile. @@ -122,10 +124,11 @@ When locking (the default, or with the \ .B dotlockfile returns the same values as the library function .IR lockfile_create (3). -Unlocking a non\-existant lockfile is not an error. +Unlocking a non\-existent lockfile is not an error. .PP If a command is executed, the return value does not correspond with that -of the command that was run. If the locking and unlocking was succesful, +of the command that was run. +If the locking and unlocking was successful, the exit status is always zero. .SH NOTES The lockfile is created exactly as named on the command line. @@ -143,7 +146,7 @@ However the command\-line arguments diff It is believed, that .I dotlockfile is the most flexible implementation, since it automatically detects when it -needs to use priviliges to lock a mailbox, and does it safely. +needs to use privileges to lock a mailbox, and does it safely. .PP The above mentioned .IR lockfile_create (3) -- 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.88-1-u1 (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 liblockfile-bin depends on: ii libc6 2.27-3 liblockfile-bin recommends no packages. liblockfile-bin suggests no packages. -- no debconf information -- Bjarni I. Gislason
