Check for lock files. There seems to be a 20 second timeout if (in my case, it was the whitelist lockfile) gets stale. Look for minutes/days old lockfiles, and clean them out.
I had steady 29+second spamd times, turned off all lookup etc, nothing changed. Snooped in the spamd users dir (I also run spamd on a remote machine with the default user 'pop3', so all bayes/whitelist info goes into that dir). Lo and behold a 15 minute old lockfile. deleted that one file and down to < 2 seconds per msg.
dual AMD 1.2Ghz, 1Gb RAM, 3 UW-SCSI 9Gb HDDs RH 9.0.
Thanks. I'll keep an eye on that. In my case I'm only using a global directory--there are no per-user files. No AWL and a single global bayes. I'll keep an eye out for lock files there.
-- _______________________________________________________________________
Rick Beebe (203) 785-6416 Manager, Systems & Network Engineering FAX: (203) 785-3481 ITS-Med Production Systems [EMAIL PROTECTED] Yale University School of Medicine Suite 124, 100 Church Street South http://its.med.yale.edu New Haven, CT 06519 _______________________________________________________________________
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
