I'm happy to change my run time again. I had it set to ~9:30UTC previously since the docs said to run at close to 9:00 UTC. I changed it to ~10:30UTC earlier this year because it seems like that caused a problem when daylight savings kicked in (no idea why, the box runs on UTC), and I'm pretty sure it still runs then (i swapped it onto a different box about a week or so ago) but I'm open to whatever time works for people.
42 10 * * * /usr/local/bin/bash /home/masscheck/bin/auto-mass-check.sh % date Sun Jul 28 07:48:33 UTC 2013 (I've got 8:49 BST on my laptop just now so within the realms of reasonable clock drift) If anyone wants to suggest a time I'll set that run, but I'm already trying to workaround a previous timing sync issue and deviating from the documentation to achieve that. Kevin On 27 Jul 2013, at 16:39, [email protected] wrote: > On 07/27, Jari Fredriksson wrote: >> 27.07.2013 12:00, [email protected] kirjoitti: >>> 20130726: Spam or ham is below threshold of 150,000: >>> http://ruleqa.spamassassin.org/?daterev=20130726 >>> 20130726: Spam: 1403764, Ham: 141335 >> I don't know, but to me it looks like batch "kpg-core" has been >> processed in different batch than anyone else, for a week now. >> >> Is it OK, or is it not? >> >> http://www.local.fi/jarif/images/ruleqa.png > > Almost certainly related to this: > https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6753 > > A workaround would be to ge kpg-core submitted at a more appropriate time. > > -- > "Eh, wisdom's overrated. I prefer beatings and snacks." > - Unity, Skin Horse > http://www.ChaosReigns.com
