[prev in list] [next in list] [prev in thread] [next in thread] 

List:       spamassassin-users
Subject:    Re: spamd running much slower than spamassassin?
From:       "Daniel J. Luke" <dluke () geeklair ! net>
Date:       2016-03-29 14:41:21
Message-ID: 0CDC4DF2-AD4A-43AF-A488-5D6593F82632 () geeklair ! net
[Download RAW message or body]

On Mar 28, 2016, at 8:57 PM, Bill Cole <sausers-20150205@billmail.scconsult.com> \
wrote:
> On 28 Mar 2016, at 14:42, Daniel J. Luke wrote:
> > On Mar 24, 2016, at 12:10 PM, Daniel J. Luke <dluke@geeklair.net> wrote:
> > > /usr/bin/time spamassassin < spam.msg
> > > 7.92 real         1.85 user         0.13 sys
> > > 
> > > /usr/bin/time spamc -U /var/run/spamd.sock < spam.msg
> > > 126.44 real         0.00 user         0.00 sys
> > 
> > well, it looks like it's DNS related, somehow.
> 
> The 2 minute pause had me thinking that, but nothing jumped out as a specific \
> explanation and nothing yet does... 
> > I'm still confused as to why 'spamassassin' doesn't have a problem but 'spamd' \
> > does. I'm running SA 3.4.1 with perl5.22.1. I've tried both downgrading Net::DNS \
> > to 0.83 and upgrading it to 1.05_2 
> > Any thoughts would be appreciated.
> 
> You haven't mentioned your platform, that I've seen, but it may be relevant, e.g. \
> historically FreeBSD jails can't do real loopback (not sure on 10.2...) EL6/7 \
> derivatives have SELinux on by default, etc... 
> So: more clues please?

Sorry, this is a Mac OS X 10.11.4 system, perl5.22.1 is self-built (perlbrew). I'm \
not sure exactly when this started, I noticed it after I upgraded to 10.11.4 from \
10.11.3, but it may have been happening before. What else would be helpful to know? 

-- 
Daniel J. Luke


[prev in list] [next in list] [prev in thread] [next in thread]