On Wed, 26 Nov 2003 14:30:02 -0500, JC <[EMAIL PROTECTED]> wrote:
> I'm going to guess that you are running spamassassin as an unprivliged
> user... Based on that, I would like to suggest that you run spamd and spamc
> on a port higher than 1024. That's what worked for me. Give it a try and let
> me know how it works out for ya.
Can anybody give me real help please????
I really appreciate your help JC, but I think you don't understand my problem very well.
It's a simple question:
It's possible that SA runs opportunistic expiry and sync at the same time(so lock failed error occurs)?
TIA
German
bayes lock failures during opportunistic expiry are normal and are not an error.
I'm not sure if SA can be attempting to synch and expire at the same time, but I do know opportunistic expiry can fail because SA is attempting to autolearn at the same time.
In general all opportunistic bayes events can, do, and will fail to acquire lock sometimes.. It's strictly a "best effort, first come first serve with fairly short timeouts" system. This is 100% normal and as-designed. The alternative is to cause massive delays in mail processing when there's a conflict between any of the opportunistic events.
------------------------------------------------------- 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
