http://bugzilla.spamassassin.org/show_bug.cgi?id=3442
------- Additional Comments From [EMAIL PROTECTED] 2004-05-28 20:46 -------
>So... Is the lock file supposed to just hang around to be flocked?
>Or is it supposed to be created/removed as the non-flock version does?
stick around. quoting the comments ;) --
# do NOT unlink! this would open a race, whereby:
#
# procA: ....unlock (unlocked lockfile)
# procB: lock (gets lock on lockfile)
# procA: unlink (deletes lockfile)
# (procB's lock is now deleted as well!)
# procC: create, lock (gets lock on new file)
#
# both procB and procC would then think they had locks, and both
# would write to the database file. this is bad.
#
# unlink ("$path.lock");
#
# side-effect: we leave a .lock file around. but hey!
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
