diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2015-09-18 15:45:38 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2015-09-21 17:15:36 +0200 |
| commit | 2190ea6c4e7f56f29fc18539284801a5f504ee48 (patch) | |
| tree | 8d4aa8f26c2912f6c53cca7bc34137d254dd9d67 /contrib/debian/examples | |
| parent | 8b2d6edaa9fbfb6344ca51edd0b3655b451cbcac (diff) | |
rpc: Split option -rpctimeout into -rpcservertimeout and -rpcclienttimeout
The two timeouts for the server and client, are essentially different:
- In the case of the server it should be a lower value to avoid clients
clogging up connection slots
- In the case of the client it should be a high value to accomedate slow
responses from the server, for example for slow queries or when the
lock is contended
Split the options into `-rpcservertimeout` and `-rpcclienttimeout` with
respective defaults of 30 and 900.
Diffstat (limited to 'contrib/debian/examples')
| -rw-r--r-- | contrib/debian/examples/bitcoin.conf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/debian/examples/bitcoin.conf b/contrib/debian/examples/bitcoin.conf index 62ffd7123a..6aae4ad4d2 100644 --- a/contrib/debian/examples/bitcoin.conf +++ b/contrib/debian/examples/bitcoin.conf @@ -73,7 +73,7 @@ # How many seconds bitcoin will wait for a complete RPC HTTP request. # after the HTTP connection is established. -#rpctimeout=30 +#rpcclienttimeout=30 # By default, only RPC connections from localhost are allowed. # Specify as many rpcallowip= settings as you like to allow connections from other hosts, |