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
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
