Bug#51953: dpkg: start-stop-daemon does not work if the binary has been replaced

[Ryan Murray <rmurray@cyberhqz.com>]

Package: dpkg
Version: 1.6.1
Severity: normal

in gdm (and other display managers) --no-restart-on-upgrade is specified to
dh_installinit, causing the daemon to keep running when it is upgraded.
(Having X suddenly die would be bad, of course).

The problem is that you are now running a process whose inode no longer exists
on the disk.  This causes start-stop-daemon (when passed the --exec) option on
a stop, to fail.

A workaround would be to not specify the --exec option to start-stop-daemon,
but that defeats the purpose of the option.

The other solution would be to change start-stop-daemon so it only checks that
the specified name is correct, not the inode where it is stored on disk.

-- System Information
Debian Release: potato
Kernel Version: Linux cyberhq 2.2.13 #1 SMP Wed Oct 20 07:46:28 PDT 1999 i686 unknown

Versions of the packages dpkg depends on:
ii  libc6           2.1.2-10       GNU C Library: Shared libraries and timezone
ii  libncurses4     4.2-3.4        Shared libraries for terminal handling