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
- Branch
- avalanche_conflicting_params
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 25931 Build 51437: Build Diff build-without-wallet · build-clang-tidy · build-clang · build-diff · build-debug · lint-circular-dependencies Build 51436: arc lint + arc unit
Event Timeline
| doc/release-notes.md | ||
|---|---|---|
| 14 | 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 | Yes that's the idea, you can still do it but you need both options. | |