On Tue, May 23, 2006 at 12:40:18PM +0200, Francesco Paolo Lovergine wrote: > klecker:~$ ps -fe|grep nscd > frankie 14797 4397 0 12:27 pts/17 00:00:00 grep nscd > klecker:~$ sudo /etc/init.d/nscd start > Starting Name Service Cache Daemon: nscd. > klecker:~$ ps -fe|grep nscd > root 14804 1 0 12:27 ? 00:00:00 /usr/sbin/nscd > frankie 14812 4397 0 12:27 pts/17 00:00:00 grep nscd > klecker:~$ sudo apt-get -u dist-upgrade > Reading package lists... Done > Building dependency tree... Done > Calculating upgrade... Done > The following packages will be upgraded: > nscd > 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > 30 not fully installed or removed. > Need to get 0B/136kB of archives. > After unpacking 0B of additional disk space will be used. > Do you want to continue [Y/n]? > Reading package fields... Done > Reading package status... Done > Retrieving bug reports... Done > Reading changelogs... Done > (Reading database ... 164331 files and directories currently installed.) > Preparing to replace nscd 2.3.6-7 (using .../archives/nscd_2.3.6-9_i386.deb) ... > Stopping Name Service Cache Daemon: nscd. > invoke-rc.d: initscript nscd, action "stop" failed. > dpkg: warning - old pre-removal script returned error exit status 1 > dpkg - trying script from the new package instead ... > Stopping Name Service Cache Daemon: nscd. > invoke-rc.d: initscript nscd, action "stop" failed. > dpkg: error processing /var/cache/apt/archives/nscd_2.3.6-9_i386.deb (--unpack): > subprocess new pre-removal script returned error exit status 1 > Starting Name Service Cache Daemon: nscd. > Errors were encountered while processing: > /var/cache/apt/archives/nscd_2.3.6-9_i386.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) If the init script fails to stop the daemon, it is *correct* to fail the upgrade as well. We should not leave old versions of daemons silently running after upgrade, this is a potential security hole. The real question here is why the init script is failing to stop nscd on your system. This may or may not warrant an RC severity; probably not, since it hasn't been reported before now. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature