Actually, the cronjob does try to restart amavisd-new but fails because
the hook is not marked executable. On 12.04, just do
chmod 755 /etc/spamassassin/sa-update-hooks.d/amavisd-new
and a successful sa-update should then trigger the restart. This looks
fixed in 12.10 later due to upstream
Actually, the cronjob does try to restart amavisd-new but fails because
the hook is not marked executable. On 12.04, just do
chmod 755 /etc/spamassassin/sa-update-hooks.d/amavisd-new
and a successful sa-update should then trigger the restart. This looks
fixed in 12.10 later due to upstream
** Changed in: spamassassin (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: spamassassin (Ubuntu)
Status: New = Triaged
--
/etc/cron.daily/spamassassin should restart amavisd
https://bugs.launchpad.net/bugs/502615
You received this bug notification because you are a member of
** Changed in: spamassassin (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: spamassassin (Ubuntu)
Status: New = Triaged
--
/etc/cron.daily/spamassassin should restart amavisd
https://bugs.launchpad.net/bugs/502615
You received this bug notification because you are a member of
Maybe you can find a version of /etc/init.d/amavis that supports reload,
the one in 9.10 doesn't:
# reload)
# echo Reloading $DESC configuration files.
# start-stop-daemon ${STOP} --signal 1
# ;;
And I believe at a maximum frequency for rule updates of once daily this
can't be
That's why I said IF it supports it. I checked and after amavis version
2.0 it is recommended one uses amavisd reload (and not HUP), which in
fact does a restart (on Karmic at least).
Maybe somebody with a little more experience with amavis should take a
look at this.
I would say if somebody
I'm wondering if it is possible to run amavisd with spamd rather than
the integrated code. That would be the only case in my opinion when your
knob makes sense. When somebody run amavisd with the integrated
SpamAssassin code (which is standard and quite possibly the only way to
do it), updating
That's what we're trying to figure out, how to tell the daemon best that
SA rules were updated. Right now indeed it makes less sense to run sa-
update when using amavis, but it still makes sense because sometimes
amavis gets restarted for other reasons, and then you'll have the
updated rules
Maybe a restart isn't such a good idea for amavis, to kill off every
child and restart at every change (could be a problem on systems under
heavy load), maybe a reload would be enough (if it supports reload).
--
/etc/cron.daily/spamassassin should restart amavisd
