On Sun, 2010-09-05 at 07:35 -0500, Shane Williams wrote: > In several places, Justin Mason has said the sysread debug line > doesn't necessarily indicate an error (he actually says they're > normal in debug mode), though these are fairly old posts. > > http://www.mail-archive.com/users@spamassassin.apache.org/msg31175.html > http://mail-archives.apache.org/mod_mbox/spamassassin-dev/200506.mbox/%3c4407.42b33d88.2f05af5b....@spamassassin.apache.org%3e > > So the sysread may be a red herring. > > On Sat, 4 Sep 2010, Chris wrote: > > > On Sat, 2010-09-04 at 08:42 -0500, Chris wrote: > >> I'm trying to figure out why I'm having ridiculous scan times such as > >> the above examples. Lower scan times such as in the 20 second range are > >> the exception rather than the rule. I'm running bind as a local caching > >> nameserver and it seems to be working correctly. I've just seen a ham > >> that has a scantime=172.2. Could there be something else on the system > >> that is affecting this?
Thanks, after reading Justin's input on the bug-report I see what's happening as far as the 'pings' go. I'll see how things go as the day progress regarding scan times. Chris -- Chris KeyID 0xE372A7DA98E6705C
signature.asc
Description: This is a digitally signed message part
