Opened 8 years ago

Closed 23 months ago

#4910 closed enhancement (wontfix)

bwauthpid has confusing parameter names

Reported by: Sebastian Owned by: aagbsn
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Blocker Keywords:
Cc: Actual Points:
Parent ID: #13630 Points:
Reviewer: Sponsor:

Description

Mike said he has given up on the bwauthpid thing, yet it is enabled by default unless bwauthpid=0 is given in a consensus. This means that for the past weeks, we've had it enabled.

Child Tickets

Change History (2)

comment:1 Changed 7 years ago by mikeperry

Owner: changed from mikeperry to aagbsn
Priority: majornormal
Status: newassigned
Summary: bwauthpid defaults to enabledbwauthpid has confusing parameter names
Type: defectenhancement

This isn't true. The parameter simply governs which code is in use. The PID codebase is capable of producing both the PID feedback results, and results compatible with the old codebase. Renaming this ticket accordingly.

comment:2 Changed 23 months ago by teor

Parent ID: #13630
Resolution: wontfix
Severity: Blocker
Status: assignedclosed

We probably won't fix this in torflow, see #13630 for a replacement, which may not even use the same pid control parameters.

Note: See TracTickets for help on using tickets.