http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3563
------- Additional Comments From [EMAIL PROTECTED] 2006-06-27 07:01 ------- After a little bit of thinking about this, I think what we'll have to do is the multiple lock thing. Something like: - if a file-based DB (DBM, etc,) and - lock_method flock when tieing read only, lock the DB with LOCK_SH. when tieing read/write, lock the DB with LOCK_EX (current behavior). Having lock_method as anything else means we'd always have to behave ala LOCK_EX, which really just kills Bayes usage, so I'd rather deal with the occasional odd behavior. One issue with this plan is that I don't know if there's a lock queue, which could potentially mean our LOCK_EX for writes may consistently time out if reads continue to keep the shared lock in place. It's probably platform dependent. Alternately, we punt this and the answer is "this behavior can happen, if you want to avoid it use SQL". Thoughts? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
