From dba4ef28cc3419a7fa87b71c2b46ea0996f94a2d Mon Sep 17 00:00:00 2001 From: Luca Boccassi Date: Wed, 21 Mar 2018 19:55:55 +0000 Subject: [PATCH] Problem: zmq_close manpage does not say it's asynchronous Solution: clarify it since it's a common source of confusion --- doc/zmq_close.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/zmq_close.txt b/doc/zmq_close.txt index 6f151edf..961d7b9e 100644 --- a/doc/zmq_close.txt +++ b/doc/zmq_close.txt @@ -29,6 +29,9 @@ NOTE: The default setting of _ZMQ_LINGER_ does not discard unsent messages; this behaviour may cause the application to block when calling _zmq_ctx_term()_. For details refer to linkzmq:zmq_setsockopt[3] and linkzmq:zmq_ctx_term[3]. +NOTE: This API will complete asynchronously, so not everything will be deallocated +after it returns. See above for details about linger. + RETURN VALUE ------------