Package: dpkg
Version: 1.14.16
Severity: critical
Quoting the changelog:
* Keep checking for the process when start-stop-daemon is called with
--retry even if the daemon removed the pidfile. Closes: #460903
This though broke s-s-d completely if you use --retry and --pidfile
together, as now s-s-d will block for the amount of time specified by
--retry, even if the process itself has stopped already.
E.g. in network-manager I have
start-stop-daemon --stop --retry 60 --quiet --pidfile $PIDFILE \
--oknodo --user $USER --exec $DAEMON
Since 1.14.16, s-s-d will block now for 60 secs *always*, although the
daemon is usually stopped withing less than a second.
I'm filing with severity critical, because now an upgrade of
network-manager will cause the update process to hang for 60 secs. Many
users will believe that it crashed or hangs and abort the
installation/upgrade.
I tested this with other daemons, and e.g. added --retry 60 to
/etc/init.d/ssh, which also caused the stop action to last 60 secs now.
Cheers,
Michael
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23.14
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dpkg depends on:
ii coreutils 5.97-5.7 The GNU core utilities
ii libc6 2.7-6 GNU C Library: Shared libraries
dpkg recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
