We have a system which uses Python multiprocessing to run multiple simulations
concurrently in child processes, with main server - child process
communication using multiprocessing. This works fine standalone.
For a GUI, we use zeromq and tornado for communications between the main server
and
You cannot continue to use zmq sockets after a fork - you have to take care
in your application that no sockets created before the fork will be used by
any calls in the child process.
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
MInRk noted that:
You cannot continue to use zmq sockets after a fork - you have to take care
in your application that no sockets created before the fork will be [not be]
used by any calls in the child process.
Thanks, that makes sense. But can anyone provide guidance in how to do that?
On Fri, Aug 30, 2013 at 11:50 AM, Townsend, Scott E. (GRC-RTM0)[Vantage
Partners, LLC] scott.e.towns...@nasa.gov wrote:
MinRK noted that:
You cannot continue to use zmq sockets after a fork - you have to
take care in your application that no sockets created before the fork will
be [not
I've been looking at a similar scenario using ruby.
As far as I can tell you cannot even touch anything relating to the parents
context in the child, including closing it. I haven't fully tested it out but
it looks to me like the pipes used for internal communication in the context
will cause
On Fri, Aug 30, 2013 at 3:12 PM, Matt Connolly matt.conno...@me.com wrote:
I've been looking at a similar scenario using ruby.
As far as I can tell you cannot even touch anything relating to the
parents context in the child, including closing it. I haven't fully tested
it out but it looks to
