Your message dated Sat, 16 Jun 2012 14:54:57 +0000
with message-id <[email protected]>
and subject line Bug#626752: fixed in lockfile-progs 0.1.15+squeeze1
has caused the Debian Bug report #626752,
regarding lockfile-progs: lockfile-create --use-pid uses wrong pid
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.)
--
626752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626752
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: lockfile-progs: lockfile-create --use-pid uses wrong pid
Package: lockfile-progs
Version: 0.1.15
Severity: grave
*** Please type your report below this line ***
From
https://bugs.launchpad.net/ubuntu/+source/lockfile-progs/+bug/676723
It uses L_PID which puts the PID of the lockfile-create process in the
lock.
It needs to use the L_PPID (2 places) to put the process id of the process
executing lockfile-create.
Without this change lockfile-create is useless, as it succeeds every time.
Spectrum of latent problems and consequences is indeed massive,
therefore severity grave.
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lockfile-progs depends on:
ii libc6 2.11.2-10 Embedded GNU C Library:
Shared lib
ii liblockfile1 1.08-4 NFS-safe locking library,
includes
lockfile-progs recommends no packages.
lockfile-progs suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lockfile-progs
Source-Version: 0.1.15+squeeze1
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:
lockfile-progs_0.1.15+squeeze1.dsc
to main/l/lockfile-progs/lockfile-progs_0.1.15+squeeze1.dsc
lockfile-progs_0.1.15+squeeze1.tar.gz
to main/l/lockfile-progs/lockfile-progs_0.1.15+squeeze1.tar.gz
lockfile-progs_0.1.15+squeeze1_amd64.deb
to main/l/lockfile-progs/lockfile-progs_0.1.15+squeeze1_amd64.deb
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.
Niels Thykier <[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: Sat, 02 Jun 2012 13:07:35 +0200
Source: lockfile-progs
Binary: lockfile-progs
Architecture: source amd64
Version: 0.1.15+squeeze1
Distribution: stable
Urgency: low
Maintainer: Rob Browning <[email protected]>
Changed-By: Niels Thykier <[email protected]>
Description:
lockfile-progs - Programs for locking and unlocking files and mailboxes
Closes: 626752
Changes:
lockfile-progs (0.1.15+squeeze1) stable; urgency=low
.
[ Niels Thykier ]
* Non-maintainer upload.
* Backport fix for #626752
.
[ Rob Browning ]
* Use L_PID rather than L_PPID when appropriate. In cases where
lockfile_create() and lockfile_check() were being called with L_PID,
use L_PPID to capture the parent's PID. Capturing the PID of the
lockfile-create or lockfile-check process made no sense. Thanks to
Zrin Žiborski <[email protected]> for the report, Larry
Diegel for the patch, and Sebastian Siewior <[email protected]>
for the suggestion to update the documentation. (Closes: #626752)
Checksums-Sha1:
90297f1b34fc036311d262e6fa17e556738c7eec 1430
lockfile-progs_0.1.15+squeeze1.dsc
6b12dfbc9633d7bd388fc944404f5440ca4e0280 138729
lockfile-progs_0.1.15+squeeze1.tar.gz
cd2aba4a65c61440462cbd04208d08a0e2a4dbd8 10680
lockfile-progs_0.1.15+squeeze1_amd64.deb
Checksums-Sha256:
5c32bcdf6dabf2957547b9b4119345a1c3fc42b7edce700feed080ea98fbf997 1430
lockfile-progs_0.1.15+squeeze1.dsc
11b72e179f53d61b5b7921568ea7a6f08718049490b22c711751f2379a3f7217 138729
lockfile-progs_0.1.15+squeeze1.tar.gz
32b26370079c6242eaaffac11f2be5ad85053ec5eaa9363514b0ff9285b2e937 10680
lockfile-progs_0.1.15+squeeze1_amd64.deb
Files:
f035624a7f473bc93e58b5dbb017661b 1430 misc optional
lockfile-progs_0.1.15+squeeze1.dsc
0c9f40d11a195cc8f4a93b9dc0c1bbb4 138729 misc optional
lockfile-progs_0.1.15+squeeze1.tar.gz
fc55c95a1d17e150c18ec0fd951f4db7 10680 misc optional
lockfile-progs_0.1.15+squeeze1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJPyfumAAoJEAVLu599gGRCqM0QAJzJiCBtqM254Cz9Yr1smu+K
tcZFHAtuBSdNgYPlEEFkBG/+rrqzalpf4021MkTa3+FJMLVKsfZyIctmqQgEElOC
OKWbIwiglt4Qd2ayh4cHvBeCMQvOiWYZEVmEHr/CWEWum0R9ddcGn9uZjeRhG2WD
lOxfq8F9B9odNqtBialRS8IkKn7uT/BjNJwDgh56Rdrz5kBIB8ghudgcX1PtXGzN
9UE1twp10AEcEPyI3z/XguTiYHPPUXvQ+Zn0Ur643XNThf7H1PC8ul1D0pjKHynY
z9YTb9bhJsxTYLVwZgk65uoC4liENkrstn7QUhgFjyHQ7raWhc9B6sMl7oxNNbe5
gyP0MBzKaEV5p6TaqurWWfNKJ6XgS/mtdGxYzQHANmVNlSOau0pRogUeWZvTMZKd
OlQpR5q90h5UYo+9rLpdv35u60O/py+3OSpsIi6fznDXCFlZKng00T1EI2gocGUF
xLftsc8wBtss4kj27kHDIGoHE2qBfp7cR+RAVr+JTA9gJ/uh8PyeKoYmXEtnJ8q+
5Rz7apPTcsiVISqyJEObq1SIijzzZim5sTnSrYNY2iWMgXV+WUvsPD5VPN8ao201
u+BFejvBeP0S8pUKojUQZnMTKt0S91e7CctHQZIUynZZwht1KAQwE/Y3QFUtfiYY
QWavWz1hcsVfcF7nJkw6
=IhuJ
-----END PGP SIGNATURE-----
--- End Message ---
