picking up #21499, author has stated they can't squash.
This adds the maxuploadtarget option to the bitcoin.conf example file. This is useful for those looking to configure their bandwidth utilization.
Changes from Original PR:
picking up #21499, author has stated they can't squash.
This adds the maxuploadtarget option to the bitcoin.conf example file. This is useful for those looking to configure their bandwidth utilization.
Changes from Original PR:
70 | @@ -71,6 +71,12 @@ 71 | # configuration option or the addnode RPC, which have a separate limit of 8 connections. 72 | #maxconnections= 73 | 74 | +# Maximum upload bandwidth target in MiB per day (e.g. 'maxuploadtarget=1024' is 1 GiB max throughput per day).
# Maximum upload bandwidth target in MiB per day (e.g. 'maxuploadtarget=1024' is 1 GiB per day).
nit: The "max throughput" is kind of redundant to the part before the parantheses, but I'm fine with either version.
I agree, drop "max throughput".
You're right, addressed in 947f973
ACK 219bbd2f52382c1b4720e8a74ded1a20676c3c9c 📝
Introduce the maxuploadtarget option to the example bitcoin.conf file. This adds visibility for this option which is useful to those looking to configure bandwidth usage.
70 | @@ -71,6 +71,12 @@ 71 | # configuration option or the addnode RPC, which have a separate limit of 8 connections. 72 | #maxconnections= 73 | 74 | +# Maximum upload bandwidth target in MiB per day (e.g. 'maxuploadtarget=1024' is 1 GiB max throughput per day). 75 | +# This limits the upload bandwidth for those with bandwidth limits. 0 = no limit (default: 0). 76 | +# Limit does not apply to peers with 'download' permission.
s/Limit/This limit/ or (probably better as it is more explicit):
# -maxuploadtarget does not apply to peers with 'download' permission.
Thanks, addressed in 947f973 by using the -maxuploadtarget suggestion
updated from 219bbd2 -> 947f973 (pr22080.01 -> pr22080.02, diff)
Changes:
ACK 947f9734daab4e47c0abdc6ef7d52812102ecb6b
re-ACK 947f9734daab4e47c0abdc6ef7d52812102ecb6b