And remove the -maxconnections option from the example config file. This options has led to several issues for avalanche users using it as a habit.
Details
Details
- Reviewers
PiRK - Group Reviewers
Restricted Project - Commits
- rABC687810ae57b5: [avalanche] Let -maxavalancheoutbound takes precedence over -maxconnections
ninja all check-all
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| doc/release-notes.md | ||
|---|---|---|
| 14 ↗ | (On Diff #43562) | if -maxavalancheoutbound is higher than -maxconnections Not sure if this is worth mentioning. Maybe users will try reducing maxavalancheoutbound to limit the number of connections. |
| doc/release-notes.md | ||
|---|---|---|
| 14 ↗ | (On Diff #43562) | Yes that's the idea, you can still do it but you need both options. |