Package: distributed-net Version: 2.9013.498-3 Severity: minor When distributed-net is stopped, it magically auto-starts on its own when the logrotate scripts are run as part of a cron job. At first I thought this was part of the package post-install due to an update. But with long uptimes and no updates, it still seemed to end up running. A quick grep revealed the logrotate call.
This results in the unexpected start. The "reload" is called clearly in the logrotate.d script weekly. I have distributed-net installed, and like to run it from time to time but have it disabled on startup. The weekly auto-start seems to not be the intent of the logrotate script and perhaps therefore a minor bug. Perhaps the reload needs to be conditional, either in logrotate.d or in the actual init.d script to ensure that if it is not already running, the logrotate script does not start it. Ian -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages distributed-net depends on: ii bind9-host [host] 1:9.3.3-1 Version of 'host' bundled with BIN ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries Versions of packages distributed-net recommends: ii logrotate 3.7.1-3 Log rotation utility -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
