zmq_ctx_term (3) - Linux Man Pages
zmq_ctx_term: destroy a 0MQ context
zmq_ctx_term - destroy a 0MQ context
The zmq_ctx_term() function shall destroy the 0MQ context context.
Context termination is performed in the following steps:
- 1. Any blocking operations currently in progress on sockets open within context shall return immediately with an error code of ETERM. With the exception of zmq_close(), any further operations on sockets open within context shall fail with an error code of ETERM.
After interrupting all blocking calls,
until the following conditions are satisfied:
- • All sockets open within context have been closed with zmq_close().
- • For each socket within context, all messages sent by the application with zmq_send() have either been physically transferred to a network peer, or the socket's linger period set with the ZMQ_LINGER socket option has expired.
For further details regarding socket linger behavior refer to the ZMQ_LINGER option in zmq_setsockopt(3).
This function replaces the deprecated function zmq_term(3).
As ZMQ_LINGER defaults to "infinite", by default this function will block indefinitely if there are any pending connects or sends. We strongly recommend to (a) set ZMQ_LINGER to zero on all sockets and (b) close all sockets, before calling this function.
- The provided context was invalid.
- Termination was interrupted by a signal. It can be restarted if needed.
This page was written by the 0MQ community. To make a change please read the 0MQ Contribution Policy at m[blue]http://www.zeromq.org/docs:contributingm.