http://bugzilla.spamassassin.org/show_bug.cgi?id=3442
------- Additional Comments From [EMAIL PROTECTED] 2004-05-29 10:05 ------- > So if unlink kills the lock, why not do lock(), then unlink() in proc A? in thinking about this some more, I'm thinking the answer is: to do the lock the process creates the file, then sits on flock(). therefore, doing the unlink won't work since the file will go away, and other processes will have issues? I really would like to change this so the lock file doesn't need to be kept around all the time, but I'm also thinking this would be ok for a 3.1 release since it's too complex for now. For 3.0, I'd be happy with a doco change making it clear that this behavior will occur if you use flock locking. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
