Your message dated Fri, 03 Sep 2021 18:04:09 +0000
with message-id <[email protected]>
and subject line Bug#747241: fixed in lockfile-progs 0.1.19
has caused the Debian Bug report #747241,
regarding lockfile-progs: lockfile-create --retry man text inaccurate
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
747241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747241
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lockfile-progs
Version: 0.1.17
Severity: normal
Dear Maintainer,
The lockfile-progs(1) man page states:
-r retry-count, --retry retry-count
Try to lock filename retry-count times before giving up. Each attempt
will be delayed a bit longer than the last (in 5 second increments)
until reaching a maximum delay of one minute between retries. If
retry-count is unspecified, the default is 9 which will give up after
180 seconds (3 minutes) if all 9 lock attempts fail.
The default value of 9 in fact results in a timeout of 3m45s (225s). A
retry-count of 8 would lead to a timeout of 180s. Either the man page
or the default retry count should be changed so that the times line up.
The times I have calculated by crude means using LibreOffice Calc are:
Retry Total wait
1 5
2 15
3 30
4 50
5 75
6 105
7 140
8 180
9 225
10 275
11 330
After 11, adding 1 to the retry counter increments the total wait by
60s, so for ~30mins wait (1830s, or 30m30s) the value should be 36.
Alternatively, for times over 6 minutes, take the total desired wait
time in minutes and add 5 to wait for 30s under the desired time, or 6
for 30s over the desired time.
HTH,
Chris
-- System Information:
Debian Release: 7.5
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lockfile-progs depends on:
ii libc6 2.13-38+deb7u1
ii liblockfile1 1.09-5
lockfile-progs recommends no packages.
lockfile-progs suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lockfile-progs
Source-Version: 0.1.19
Done: Rob Browning <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lockfile-progs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rob Browning <[email protected]> (supplier of updated lockfile-progs
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 03 Sep 2021 12:40:55 -0500
Source: lockfile-progs
Architecture: source
Version: 0.1.19
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning <[email protected]>
Changed-By: Rob Browning <[email protected]>
Closes: 747241
Changes:
lockfile-progs (0.1.19) unstable; urgency=medium
.
* Fix lockfile-progs(1) --retry timeout example value. Thanks to Chris
Boot for reporting the issue. (Closes: 747241)
.
* Update lockfile-progs(1) version to 0.1.19.
.
* Include -fwrapv and -fno-strict-aliasing in default CFLAGS.
Checksums-Sha1:
daf6cd393a8ea6a55da4c72b01d0c39101cde928 1474 lockfile-progs_0.1.19.dsc
f768468e759eac7304221c57afb8bc67a1fec4a1 104345 lockfile-progs_0.1.19.tar.gz
7c991fa6ac43e0879850c54203f90ca47b75fa0c 6419
lockfile-progs_0.1.19_amd64.buildinfo
Checksums-Sha256:
999267049f4b88a80b6f9f88a535aeee277110a603e790cf49e4de7c55d520a9 1474
lockfile-progs_0.1.19.dsc
2c5704b01c8f474f82921780e4592a927b2bf6a6d7616354a6c5d7cd5664857e 104345
lockfile-progs_0.1.19.tar.gz
4681ab224127f132d353b4186f2dcf40b9d912a60868403570a2b17d3738b221 6419
lockfile-progs_0.1.19_amd64.buildinfo
Files:
b65ad08ac3c45719c87383052c4fb5d8 1474 misc optional lockfile-progs_0.1.19.dsc
3a18932a04a1a706f6b2e05e0f50e3c2 104345 misc optional
lockfile-progs_0.1.19.tar.gz
f4c850cbaa4b13f25a5b9c2997a04f0b 6419 misc optional
lockfile-progs_0.1.19_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCAAzFiEEPTFSABe5ruOuhW+97vEWxVpaQvEFAmEyYCQVHHJsYkBkZWZh
dWx0dmFsdWUub3JnAAoJEO7xFsVaWkLxIs0QAIIFexyYdjnf2VXqMCqu+6rBNxep
n2oi/1S/Qg9UAiugOSWlCS6w5CuhMucK3ajF1W9bKPoF4LNIQUh2F/fuUhKl0PaF
i34zFZZMiexV7E1UCaC66RScVhLEVNC5D9EvuUIrXKpfBAGmXc+68qCY6we+lXgS
CWoH9NLOlGxVC/wIJnTXmbO/P7or9vBZ7rZ8KivYdouqX7en7Jwd/6+arwOfiMR1
vuZVNrV6Wq1JqqAJaKuJRUEbnO+JMAfNX96bk+qkMpeEr8PB3m0x1oLAXbO7lB/s
iyh2U2pLc4h7Im/Vb9hdz5GiXlfw4MsnK0scUMeCwhG84orBEKdQwQ2EU06zACiY
DJC5j9nS6S2hoH+wVCE5xlPeuL6HxIVIPxr+Ijfl5MVgHdRDBNTMzdmB7sqaifu0
mVHmUG65oxo/oTQ0jyym7ep8gLDmHZtxRJVe8w1GnNg4aRg/RMHkxKRH7LyTyMXD
TsUIo1RQ9bNGIqqhdlYSNyF/sO7gSVyXv9JF4P6t7BkkzdIN9TTius/1+kw7pXpg
rPjck+tMgNViaKmAwIqXyi1XvgUjR9qcX/BAf5rmB8ebMYuodY3GhT6DWKBGR0Gu
CVsUs3RljgDAevumkoWzEmjHqgUEnHZ/EJ3Q3d4WBIf6cW0dbuD2wFli+nVBliXB
YauA18c+17PRgL1T
=8Sqx
-----END PGP SIGNATURE-----
--- End Message ---
