The sa-update cron script in line 48 sleeps for a random amount of time (up to two hours!). This is actually unnecessary since spamassassin checks whether a new ruleset is available for download using DNS (eg. "host -t TXT 1.4.3.updates.spamassassin.org" for Version 3.4.1) That means by using a custom TTL on the TXT entries the provider of the channel gets to decide how often your DNS cache is to hammer their upstream DNS server and then, only if DNS actually indicates there is an update, the sa-update mechanism contacts the server via HTTP(S) to download the rulesets. So in theory you could run the script every second and unless the TTL is expired you're only really pestering your local DNS cache. I opt for removing this sleep call as it is unnecessary and confusing when invoking the script after adding channels.
Thats one side of it, but not the other... in the event there _is_ an update every fedora instance out there will hit the http server at once (since the cron job runs at the same time) possibly swamping it. Or did I miss what you are proposing here?
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.