On at least two separate occasions, apt-proxy has failed to start back up after logrotate signals it to restart.
The machine is a 533 MHz P3, so I'm not terribly surprised that apt-proxy takes longer than a second to shut down. Would the --retry option to start-stop-daemon help matters? It seems as though it should ensure that apt-proxy has totally shut down before restarting, but I could be misreading the man page. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-p3-1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages apt-proxy depends on: ii bzip2 1.0.2-1 A high-quality block-sorting file ii debconf 1.4.30.11 Debian configuration management sy ii logrotate 3.7-2 Log rotation utility ii python 2.3.4-5 An interactive high-level object-o ii python-apt 0.5.10 Python interface to libapt-pkg ii python-bsddb3 3.3.0-6 Python interface to libdb3 ii python-twisted 1.3.0-6 Event-based framework for internet -- debconf information: apt-proxy/upgrading-v2: apt-proxy/upgrading-v2-result: -- Charles Lepple
