Cron ~/svn/trunk/build/mkupdates/run_nightly | /usr/bin/tee /var/www/automc.spamassassin.org/mkupdates/mkupdates.txt

2018-03-26 Thread Cron Daemon
+ promote_active_rules + pwd + /usr/bin/perl build/mkupdates/listpromotable /usr/local/spamassassin/automc/svn/trunk HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1 HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1 day 2 contains a --net mass-check! offsetting by an extra day Use

Re: [Bug 7566] "SHA1 verification failed" for sa-update.razx.cloud since 1-2 weeks

2018-03-26 Thread Kevin A. McGrail
Until we have a good score file, while publish the file anyway? DNS should stay with the last known good file. I would generate the tick file some where temporary, then update it with the tock data and publish/update DNS. The mirrors shouldn't even see the temporary file. Thoughts? KAM That -

Re: [Bug 7566] "SHA1 verification failed" for sa-update.razx.cloud since 1-2 weeks

2018-03-26 Thread Dave Warren
This seems to make sense from here (as a sysadmin. As a mirror operator I don't care). On 2018-03-26 14:46, Kevin A. McGrail wrote: Until we have a good score file, while publish the file anyway? DNS should stay with the last known good file. I would generate the tick file some where temporary

Re: [Bug 7566] "SHA1 verification failed" for sa-update.razx.cloud since 1-2 weeks

2018-03-26 Thread Bill Cole
On 26 Mar 2018, at 16:46, Kevin A. McGrail wrote: I would generate the tick file some where temporary, then update it with the tock data and publish/update DNS. The mirrors shouldn't even see the temporary file. Thoughts? I don't think the current model is seriously harmful, since the score