From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-api 1/1] d/triggers: add interest in spamassassin updates
Date: Wed, 12 Jun 2024 19:10:17 +0200 [thread overview]
Message-ID: <20240612171018.18240-2-s.ivanov@proxmox.com> (raw)
In-Reply-To: <20240612171018.18240-1-s.ivanov@proxmox.com>
currently an update to SpamAssassin does not reload any of the
services.
This patch simply adds interest-noawait on a trigger activated by
proxmox-spamassassin, which in turn reloads all services (as already
done for updates to pve-common, and in PVE on updates on other
packages that affect the API).
Technically it might only be necessary to reload pmg-smtp-filter,
pmgproxy and pmgdaemon, to get the benefits of a new spamassassin
version, but reloading all services seems more robust in the long run.
[0] https://git.dpkg.org/cgit/dpkg/dpkg.git/tree/doc/spec/triggers.txt
[1] https://manpages.debian.org/bookworm/dpkg-dev/deb-triggers.5.en.html
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
debian/triggers | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/triggers b/debian/triggers
index aabe418..0d01133 100644
--- a/debian/triggers
+++ b/debian/triggers
@@ -1 +1,2 @@
interest-noawait pve-api-updates
+interest-noawait pmg-sa-updates
--
2.39.2
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
next prev parent reply other threads:[~2024-06-12 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 17:10 [pmg-devel] [PATCH spamassassin/pmg-api] add trigger to reload pmg-api services on " Stoiko Ivanov
2024-06-12 17:10 ` Stoiko Ivanov [this message]
2024-06-12 17:10 ` [pmg-devel] [PATCH spamassassin 1/1] d/triggers: add trigger to restart pmg services Stoiko Ivanov
2025-02-21 17:38 ` [pmg-devel] applied-series: [PATCH spamassassin/pmg-api] add trigger to reload pmg-api services on spamassassin updates Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240612171018.18240-2-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.