Excerpts from Edward Z. Yang's message of lun sep 03 02:00:59 -0300 2012: > The locking is a downright crime (where's the STM when you need it), > and it's still racy, but it should work OK.
Hm. I tried this but ran into trouble: I currently run branch "next", and your patch doesn't apply there; so I tried your ~ezyang fork and branch maildir-sync there, but I find that when in that branch (with or without this patch), Sup seems to eat 100% of a CPU core doing clock_gettime() and select() continuously. Not sure what's happening. I assume you don't see that behavior. -- Álvaro Herrera <alvhe...@alvh.no-ip.org> _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel
