Mercurial > hg > freeDiameter
comparison doc/rt_busypeers.conf.sample @ 1108:7ee7b95701c9
Change the rt_busy parameter to milliseconds
| author | Sebastien Decugis <sdecugis@freediameter.net> |
|---|---|
| date | Mon, 13 May 2013 09:46:39 +0800 |
| parents | 8110a781116a |
| children |
comparison
equal
deleted
inserted
replaced
| 1107:96f2051215c8 | 1108:7ee7b95701c9 |
|---|---|
| 37 # Default: 0, meaning all possible candidates are attempted before give up. | 37 # Default: 0, meaning all possible candidates are attempted before give up. |
| 38 #RetryMaxPeers=0; | 38 #RetryMaxPeers=0; |
| 39 | 39 |
| 40 | 40 |
| 41 # Parameter: RelayTimeout | 41 # Parameter: RelayTimeout |
| 42 # If the value of this parameter is not 0, it specifies the number of seconds that the local relay waits for an answer to a | 42 # If the value of this parameter is not 0, it specifies the number of milliseconds (1/1000 s) that the local relay waits for an answer to a |
| 43 # forwarded request before considering the remote peer is busy and taking corrective action (similar as if that relay had returned TOO_BUSY status). | 43 # forwarded request before considering the remote peer is busy and taking corrective action (similar as if that relay had returned TOO_BUSY status). |
| 44 # Note: this parameter does not apply for requests issued locally. In that case, the extension issuing the request should directly specify the timeout. | 44 # Note: this parameter does not apply for requests issued locally. In that case, the extension issuing the request should directly specify the timeout. |
| 45 # Default: 0, meaning that there is no timeout parameter. | 45 # Default: 0, meaning that there is no timeout parameter. |
| 46 #RelayTimeout=0; | 46 #RelayTimeout=0; |
| 47 | 47 |