Package: spamassassin
Version: 3.4.0-2
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.
The is really something of a more general problem with start-stop-daemon
and maybe this bug should be reassigned to dpkg, but I encountered it
with spamd and I'll let you decide.
In my particular case, prelink also had a hand in the situation, so it's
not just package upgrades that can trigger it:
lrwxrwxrwx 1 root root 0 Aug 6 10:34 exe -> /usr/bin/perl.#prelink#.WTKInn
(deleted)
To reproduce:
# cp -a /usr/bin/perl{,2}
# mv /usr/bin/perl{2,}
# /etc/init.d/spamassassin restart
Thank you!
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
