On Sun, 2 Jun 2019 at 18:04, Kevin A. McGrail wrote:
> with just the cron log output :-)
>
I don't know to commend you or commit you ;-)
I appreciate the noise.
For the record, when the system catastrophically failed, I rebuilt it
from the ground up on a new server with just the cron log output :-)
On 6/2/2019 3:41 AM, Paul Stead wrote:
> Looks good now - I've made the lock fail error a bit quieter but the lock
> fails since my la
+ promote_active_rules
+ pwd
/usr/local/spamassassin/automc/svn/trunk
+ svn co https://svn.apache.org/repos/asf/spamassassin/trunk/rulesrc
Checked out revision 1860506.
+ /usr/bin/perl build/mkupdates/listpromotable
HTTP get: https://ruleqa.spamassassin.org/1-days-ago?xml=1
day 1 contains a --net m
Hopefully squashed this one - it looks to be the output from the ruleqa.cgi
-refresh cal
On 2019/06/02 07:47:21, r...@sa-vm1.apache.org (Cron Daemon) wrote:
> /usr/local/bin/runRuleQArefresh.sh: line 71: 0: command not found
>
/usr/local/bin/runRuleQArefresh.sh: line 71: 0: command not found
Looks good now - I've made the lock fail error a bit quieter but the lock
fails since my last email are valid - just the hourly is running for long
time -
---8<---
automc 20493 5.3 0.1 43140 21496 ?SN 04:05 11:34
/usr/bin/perl -w
/usr/local/spamassassin/automc/svn/masses/rule-qa/co
