Bug#396944: start-stop-daemon can't stop process

[Kurt Roeckx]

On Tue, Aug 28, 2007 at 04:12:05PM -0600, Bruce Sass wrote:
> 
> ps reports the exim4 daemon to be process 1685,
> and s-s-d finds 1685 to be /usr/sbin/.nfs00035c1d000000a3
> [see the debian-dpkg post mentioned at the top of this message]
> 
> $ ls -l /usr/sbin/.nfs00035c1d000000a3
> -rwsr-xr-x 1 root root 672764 Jul 14 01:42 /usr/sbin/.nfs00035c1d000000a3
> 
> # zgrep "exim4-daemon-light" dpkg.log*
> dpkg.log:2007-08-24 02:59:01 upgrade exim4-daemon-light 4.67-7 4.67-8
> ...
> dpkg.log.1:2007-07-17 00:40:24 upgrade exim4-daemon-light 4.67-5 4.67-7
> ...
> dpkg.log.2.gz:2007-06-18 22:15:10 upgrade exim4-daemon-light 4.67-1 4.67-3
> ...
> 
> $ ls -l /var/log/dmesg
> -rw-r--r-- 1 root adm 14642 Jul 26 01:55 dmesg
> 
> So, /usr/sbin/exim4 changed on disk prior to the previous (successful,
> 2007-07-17) upgrade and it survived a reboot.

So what I get from this is:
2007-07-14: exim4 4.67-7 is uploaded to unstable
2007-07-17: exim4 is upgraded from 4.67-5 to 4.67-7
2007-07-26: machine is rebooted
2007-08-19: exim4 4.67-8 is uploaded to unstable
2007-08-24: exim4 is upgraded from 4.67-7 to 4.67-8

On 2007-08-24 the daemon (from 4.67-7) got renamed to
/usr/sbin/.nfs00035c1d000000a3, and a new one got installed
in it's place.  /usr/sbin/.nfs00035c1d000000a3 still has the
date from when it's uploaded to unstable.

This all looks normal to me.


Kurt