On Wed, Feb 16, 2011 at 3:47 PM, Chuck Remes <[email protected]> wrote:
> ... > and how I solved it. tl;dr :) > 1. The publisher pushed too much data to its socket... > I fixed it by finally detecting and repairing the "weekend clock skip" bug. > So it's not really "fixed" in the 0mq library; I just avoid the condition Indeed... the problem is still there and will come back to hit someone. Nothing you've said suggests it's an OS X issue. If your hypothesis #1 is correct it should be easy to reproduce with a minimal publisher and subscribers, not even needing a reactor. Could you explain in pure 0MQ terms a scenario you think would provoke this, and I'll whip up a test case and see if I can make it die on Linux. Cheers -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
