https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6876
Bug ID: 6876
Summary: Partial / diff sync for sa-update
Product: Spamassassin
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: sa-update
Assignee: [email protected]
Reporter: [email protected]
Classification: Unclassified
Creating this ticket to ensure the issue is not lost in the e-mail discussion
around the sa-update mirrors:
| I noticed that there are some IPs who download every 5
| to 20 minutes (and are actually downloading, eg
| 1395916.tar.gz at 251213 bytes according to the Apache
| log). I'm sure it is worse on the other mirrors.
We have no ability to know that this isn't just firewalling.
We know from tickets that some installations have hundreds
and hundreds of servers so this could be correct.
| Should this be limited? And if yes, within sa-update or
| on the infrastructure level?
It's been debated and debated with no good answer how to
limit it. At worst, perhaps making sa-update only download
(not check) one time per day via a file that's created and
if it's not 23 hours old, the proggy aborts? It's easy for
Admin's to work around if they need but serves as a simple
barrier for those whose installations might have gone wacky.
| It's a bit the same effect we had back when we allowed
| transfer of the dnswl.org zone files via HTTP. There, we
| moved completely to using rsync, which I don't believe is
| an option for sa-update (or is there a "native Perl"
| implementation of an rsync client?).
For me, I want to keep things simpler so we can keep things
running with minimal oversight.
--
You are receiving this mail because:
You are the assignee for the bug.
