aboutsummaryrefslogtreecommitdiff
path: root/LICENSE
diff options
context:
space:
mode:
authormoneromooo-monero <moneromooo-monero@users.noreply.github.com>2018-09-03 14:19:15 +0000
committermoneromooo-monero <moneromooo-monero@users.noreply.github.com>2018-09-29 08:44:18 +0000
commit734030046055f521a73e59b50fa2a16f48e34c8d (patch)
tree7f7f8b4d50b8a0138c3c22d39d447ca0a85d45b1 /LICENSE
parentMerge pull request #4423 (diff)
downloadmonero-734030046055f521a73e59b50fa2a16f48e34c8d.tar.xz
add --block-notify to monerod and --tx-notify to monero-wallet-{cli,rpc}
Those take a command line of the form "A [B]", with A being the name (and optional path, if not in the caller's CWD, but fully qualified path is recommended, avoids possible security issues) to a program, and optional arguments. Any occurence of the two character string "%s" will be replaced by the hash of the block or transaction which triggered the notification. Tokenization is barebones. If you want things like pipes, calls to paths with spaces, etc, then use a script (though exec time will suffer). block-notify is called when a new block is added onto the chain. tx-notify is called when a new transaction happens with the wallet as source and/or destination. It is the notification program's responsibility to determine what to do in those cases. Note that this is asynchronous, so it is very possible that: - the notification programs will be run out of order - several events happen before the notification for the first one A Windows port would be nice if someone wants to make one.
Diffstat (limited to 'LICENSE')
0 files changed, 0 insertions, 0 deletions