Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

zmq_term(3) [debian man page]

ZMQ_TERM(3)							    0MQ Manual							       ZMQ_TERM(3)

NAME
zmq_term - terminate 0MQ context SYNOPSIS
int zmq_term (void *context); DESCRIPTION
The zmq_term() function shall terminate 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. 2. After interrupting all blocking calls, zmq_term() shall block until the following conditions are satisfied: o All sockets open within context have been closed with zmq_close(). o 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 behaviour refer to the ZMQ_LINGER option in zmq_setsockopt(3). RETURN VALUE
The zmq_term() function shall return zero if successful. Otherwise it shall return -1 and set errno to one of the values defined below. ERRORS
EFAULT The provided context was invalid. EINTR Termination was interrupted by a signal. It can be restarted if needed. SEE ALSO
zmq(7) zmq_init(3) zmq_close(3) zmq_setsockopt(3) AUTHORS
This manual page was written by the 0MQ community. 0MQ 2.2.0 04/04/2012 ZMQ_TERM(3)

Check Out this Related Man Page

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. Note The default setting of ZMQ_LINGER does not discard unsent messages; this behaviour may cause the application to block when calling zmq_term(). For details refer to zmq_setsockopt(3) and zmq_term(3). 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 The provided socket was invalid. SEE ALSO
zmq_socket(3) zmq_term(3) zmq_setsockopt(3) zmq(7) AUTHORS
This manual page was written by the 0MQ community. 0MQ 2.2.0 04/04/2012 ZMQ_CLOSE(3)
Man Page

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Abnormal Termination errors

I'm having trouble with Abnormal Termination errors. What are they, what causes them and how can I prevent them from happening? Are they application specific? (2 Replies)
Discussion started by: bialsibub
2 Replies

2. UNIX for Dummies Questions & Answers

Which application has a TCP socket open

If I do a netstat -a I can see all the sockets currently open, is there a way that I can tell which application is holding open these sockets ? (3 Replies)
Discussion started by: murphyboy
3 Replies

3. Shell Programming and Scripting

Get the number of open sockets weblogic

Hi, i am trying to getting the total number of currently open sockets, so i can make an IF statement to see if its over 300 and send a alert. I looked in this page docs.oracle.com/cd/E13222_01/wls/docs81/admin_ref/admin_refIX.html But i didnt find something to get the number of open... (0 Replies)
Discussion started by: axeelcs
0 Replies