https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6996
Kevin A. McGrail <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Target Milestone|Undefined |3.4.0 Severity|major |blocker --- Comment #1 from Kevin A. McGrail <[email protected]> --- >From discussing with Mark, this is a blocker for 3.4.0 Mark: > What used to be a rarely- > occuring bug that went by unnoticed, will turn into a likely stall with > only one process remaining available for all but one socket (e.g. on a > dual-stack host with spamd listening on both IP addresses of a loopback > interface). > > I'd say it is a blocker. We may not bother with Windows-locking and > just implement a simple flock, which is cheap and works well on Unix > using a local (non-NFS) lock file, and automatically unlocks if a process > happens to crash while holding a lock. My only thought perhaps them we should make an if (windows) loop and if ip4 and v6, then round-robin is not available option as well? Beyond that, the work around is trivial and I don't think has a huge impact on the product. Looking at bug 4594, I think is the one I'm remembering. -- You are receiving this mail because: You are the assignee for the bug.
