On Fri, Aug 29, 2014 at 02:21:43AM -0400, sacrificial-spam-addr...@horizon.com 
wrote:
> When installing the recent Perl 5.20 upgrade, I noticed that
> /etc/init.d/spamassassin wasn't restarting spamd.  Even though the
> $PIDFILE was correct.
> 
> This is because the interpreter was no longer named /usr/bin/perl, and
> so the "--exec $XNAME" condition refused to believe it, did not stop
> the daemon, and the new one couldn't start because the socket was in use.

Looking at some of the packaging, I wonder if there might actually be a
problem with spamassassin that's causing this instead. When I split
sa-compile out into a different package, I moved the recompile actions
into sa-compile's postinst. However, I didn't indicate sa-compile's
interest in the perl-major-upgrade trigger, so this postinst action will
never get performed. spamassassin itself no longer performs any action
on the perl-major-upgrade trigger.

Regardless of whether or not fixing the above issue is enough to resolve
this bug, it will prevent the hook from working as expected and is a
bug. I'll see about confirming that things work as expected when that
bug is fixed.

noah

Attachment: signature.asc
Description: Digital signature

Reply via email to