Man page - zmq_close(3)
Packages contas this manual
- zmq_connect(3)
- zmq_ipc(7)
- zmq_atomic_counter_new(3)
- zmq_vmci(7)
- zmq_null(7)
- zmq_atomic_counter_inc(3)
- zmq_ctx_set(3)
- zmq_disconnect(3)
- zmq_plain(7)
- zmq_socket(3)
- zmq_bind(3)
- zmq_z85_decode(3)
- zmq_curve_keypair(3)
- zmq_atomic_counter_destroy(3)
- zmq_msg_set_routing_id(3)
- zmq_tipc(7)
- zmq_poll(3)
- zmq_version(3)
- zmq_recv(3)
- zmq_socket_monitor_versioned(3)
- zmq_gssapi(7)
- zmq_msg_set(3)
- zmq_curve(7)
- zmq_inproc(7)
- zmq_socket_monitor(3)
- zmq_ctx_shutdown(3)
- zmq_atomic_counter_value(3)
- zmq_proxy_steerable(3)
- zmq_poller(3)
- zmq_getsockopt(3)
- zmq_setsockopt(3)
- zmq_msg_move(3)
- zmq_send_const(3)
- zmq_udp(7)
- zmq_proxy(3)
- zmq_errno(3)
- zmq_msg_size(3)
- zmq_msg_routing_id(3)
- zmq_msg_more(3)
- zmq_recvmsg(3)
- zmq_msg_recv(3)
- zmq_timers(3)
- zmq_z85_encode(3)
- zmq_atomic_counter_set(3)
- zmq_msg_init_size(3)
- zmq_ctx_term(3)
- zmq_msg_send(3)
- zmq_msg_data(3)
- zmq_has(3)
- zmq_msg_gets(3)
- zmq_msg_init_data(3)
- zmq_unbind(3)
- zmq_atomic_counter_dec(3)
- zmq_ppoll(3)
- zmq_ctx_new(3)
- zmq_msg_init_buffer(3)
- zmq_msg_close(3)
- zmq_send(3)
- zmq_msg_copy(3)
- zmq(7)
- zmq_ctx_get(3)
- zmq_pgm(7)
- zmq_msg_get(3)
- zmq_sendmsg(3)
- zmq_close(3)
- zmq_curve_public(3)
- zmq_connect_peer(3)
- zmq_tcp(7)
- zmq_strerror(3)
- zmq_msg_init(3)
apt-get install libzmq3-dev
Manual
| ZMQ_CLOSE(3) | 0MQ Manual | ZMQ_CLOSE(3) |
NAME
zmq_close - close 0MQ socket
SYNOPSIS
int zmq_close (void *socket);
DESCRIPTION
The zmq_close() function shall destroy the socket referenced by the socket argument. Any outstanding messages physically received from the network but not yet received by the application with zmq_recv() shall be discarded. The behaviour for discarding messages sent by the application with zmq_send() but not yet physically transferred to the network depends on the value of the ZMQ_LINGER socket option for the specified socket.
zmq_close() must be called exactly once for each socket. If it is never called, zmq_ctx_term() will block forever. If it is called multiple times for the same socket or if socket does not point to a socket, the behaviour is undefined.
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 zmq_setsockopt(3) and 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
The zmq_close() function shall return zero if successful. Otherwise it shall return -1 and set errno to one of the values defined below.
ERRORS
ENOTSOCK
SEE ALSO
zmq_socket(3) zmq_ctx_term(3) zmq_setsockopt(3) zmq(7)
AUTHORS
This page was written by the 0MQ community. To make a change please read the 0MQ Contribution Policy at http://www.zeromq.org/docs:contributing.
| 10/29/2024 | 0MQ 4.3.5 |