Re: [zeromq-dev] multiprocessing forked children kill zeromq server

2013-08-30 Thread MinRK
On Fri, Aug 30, 2013 at 3:12 PM, Matt Connolly 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 me like the pip

[zeromq-dev] non-clean exit - "Context was terminated"

2013-08-30 Thread Chris Laws
I am learning zeromq and have built a small-ish application using czmq that generally works well. However, when I shut it down using Ctrl+C, it prints "Context was terminated" to standard out. I presume this indicates a non-clean exit and I would like to fix this. I have read the guide section abo

Re: [zeromq-dev] multiprocessing forked children kill zeromq server

2013-08-30 Thread Matt Connolly
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 m

Re: [zeromq-dev] Is ZMQ_PLAIN authentication supposed to do anything?

2013-08-30 Thread MinRK
On Fri, Aug 30, 2013 at 1:37 PM, Pieter Hintjens wrote: > On Thu, Aug 29, 2013 at 1:32 AM, MinRK wrote: > > > Thanks. By closed, you mean the connecting peer (client) should be > closed, > > or the inner pipe on the server side? What should be the user-visible > > symptoms of failed authenticat

Re: [zeromq-dev] Is ZMQ_PLAIN authentication supposed to do anything?

2013-08-30 Thread Pieter Hintjens
On Thu, Aug 29, 2013 at 1:32 AM, MinRK wrote: > Thanks. By closed, you mean the connecting peer (client) should be closed, > or the inner pipe on the server side? What should be the user-visible > symptoms of failed authentication, both on the client side and the server > side, if any? I'm looki

Re: [zeromq-dev] multiprocessing forked children kill zeromq server

2013-08-30 Thread MinRK
On Fri, Aug 30, 2013 at 11:50 AM, Townsend, Scott E. (GRC-RTM0)[Vantage Partners, LLC] 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 be] used by any calls

[zeromq-dev] multiprocessing forked children kill zeromq server

2013-08-30 Thread Townsend, Scott E. (GRC-RTM0)[Vantage Partners, LLC]
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?

Re: [zeromq-dev] multiprocessing forked children kill zeromq server

2013-08-30 Thread MinRK
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 http://lists.z

[zeromq-dev] multiprocessing forked children kill zeromq server

2013-08-30 Thread Townsend, Scott E. (GRC-RTM0)[Vantage Partners, LLC]
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 an

[zeromq-dev] curvezmq : check hello signature with state machine management

2013-08-30 Thread Laurent Alebarde
Hi Pieter, I have added a few lines of code to make use of the comparison with the expected signature in process_hello. The propose code resets the server state machine if it fails. If you wish, I can make a pull request. Cheers, Laurent. ___ ze