Right. What I'm finding is that 0MQ doesn't treat the inetd server as a valid peer, for some reason, and reconnects over and over... my client doesn't have time to complete a ZMTP handshake before it's interrupted. Your solution avoids using 0MQ at all over inetd.
I'll try a few more things. How critical is this? -Pieter On Sat, Nov 10, 2012 at 8:26 AM, Shane Spencer <[email protected]> wrote: > OK.. No laughies. Here's my sample approach for spinning up workers > from a tornado instance using InetD > > https://gist.github.com/4048989 > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
