Package: spamassassin Version: 3.0.2-1 Severity: important If I use /etc/init.d/spamassassin reload to let spamd reload its settings, I will end up with no spamd running. The logs show 'correct behaviour':
2005-02-23 15:40:19 [12191] i: server hit by SIGHUP, restarting 2005-02-23 15:40:19 [12191] i: child 12196 killed successfully 2005-02-23 15:40:19 [12191] i: child 12199 killed successfully 2005-02-23 15:40:19 [12191] i: child 12198 killed successfully 2005-02-23 15:40:19 [12191] i: child 12197 killed successfully 2005-02-23 15:40:19 [12191] i: child 12195 killed successfully But then also the 'mother' dies (wihout any news in the logs). grts Tim -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9 Locale: LANG=nl_NL, LC_CTYPE=nl_NL (charmap=UTF-8) (ignored: LC_ALL set to nl_NL.UTF-8) Versions of packages spamassassin depends on: ii debconf 1.4.30.11 Debian configuration management sy ii libdigest-sha1-perl 2.10-1 NIST SHA-1 message digest algorith ii libhtml-parser-perl 3.45-1 A collection of modules that parse ii perl [libstorable-perl] 5.8.4-5 Larry Wall's Practical Extraction ii spamc 3.0.2-1 Client for SpamAssassin spam filte -- debconf information: spamassassin/upgrade/2.40: spamassassin/upgrade/2.40w: spamassassin/upgrade/cancel: Continue spamassassin/upgrade/2.42m: No spamassassin/upgrade/2.42u: No -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
