diff options
| author | Martin Sustrik <sustrik@fastmq.commkdir> | 2010-01-19 12:48:38 +0100 |
|---|---|---|
| committer | Martin Sustrik <sustrik@fastmq.commkdir> | 2010-01-19 12:48:38 +0100 |
| commit | 6b0457fcaad3fa9a2e632b3799119c40da8dd6ca (patch) | |
| tree | bbd62d2df595869d0fb3a633169226e951a43d13 | |
| parent | 7094edd6baf0d69c3879da7f16c7222388952931 (diff) | |
minor documentation patch
| -rw-r--r-- | man/man3/zmq_setsockopt.3 | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/man/man3/zmq_setsockopt.3 b/man/man3/zmq_setsockopt.3 index f419f78..f1dd9cb 100644 --- a/man/man3/zmq_setsockopt.3 +++ b/man/man3/zmq_setsockopt.3 @@ -18,15 +18,15 @@ mark cannot be exceeded. If the messages don't fit into the pipe emergency mechanisms of the particular socket type are used (block, drop etc.) If HWM is set to zero, there are no limits for the content of the pipe. -Type: int64_t Unit: bytes Default: 0 +Type: int64_t Unit: messages Default: 0 .IP "\fBZMQ_LWM\fP" Low watermark makes sense only if high watermark is defined (i.e. is non-zero). When the emergency state is reached when messages overflow the pipe, the -emergency lasts till the size of the pipe decreases to low watermark. -At that point normal state is resumed. +emergency lasts at most till the size of the pipe decreases to low watermark. +Normal state is resumed at that point. -Type: int64_t Unit: bytes Default: 0 +Type: int64_t Unit: messages Default: 0 .IP "\fBZMQ_SWAP\fP" Swap allows the pipe to exceed high watermark. However, the data are written @@ -126,7 +126,7 @@ to the appropriate value. unknown option, a value with incorrect length or invalid value. .SH EXAMPLE .nf -int rc = zmq_setsockopt (s, ZMQ_SUBSCRIBE, "*", 1); +int rc = zmq_setsockopt (s, ZMQ_SUBSCRIBE, "", 0); assert (rc == 0); .fi .SH SEE ALSO |