aboutsummaryrefslogtreecommitdiff
path: root/doc/zmq.md
diff options
context:
space:
mode:
authornthumann <me@n-thumann.de>2020-03-11 00:13:02 +0100
committernthumann <me@n-thumann.de>2020-09-23 23:14:28 +0200
commitb1c3f180ecb63f3960506d202feebaa4271058ae (patch)
tree4268fd33e7541789eb822987fe656f0ffcdeca13 /doc/zmq.md
parent347c94f551c3f144c44e00373e4dd61ff6d908b7 (diff)
downloadbitcoin-b1c3f180ecb63f3960506d202feebaa4271058ae.tar.xz
doc: Adjust ZMQ usage to support multiple interfaces
Diffstat (limited to 'doc/zmq.md')
-rw-r--r--doc/zmq.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/zmq.md b/doc/zmq.md
index f003c90d3a..85f3370130 100644
--- a/doc/zmq.md
+++ b/doc/zmq.md
@@ -67,6 +67,7 @@ Currently, the following notifications are supported:
The socket type is PUB and the address must be a valid ZeroMQ socket
address. The same address can be used in more than one notification.
+The same notification can be specified more than once.
The option to set the PUB socket's outbound message high water mark
(SNDHWM) may be set individually for each notification:
@@ -82,6 +83,7 @@ The high water mark value must be an integer greater than or equal to 0.
For instance:
$ bitcoind -zmqpubhashtx=tcp://127.0.0.1:28332 \
+ -zmqpubhashtx=tcp://192.168.1.2:28332 \
-zmqpubrawtx=ipc:///tmp/bitcoind.tx.raw \
-zmqpubhashtxhwm=10000