Opened 8 years ago

Closed 5 years ago

#2170 closed task (worksforme)

Consistent place to configure socket file paths

Reported by: shane Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: Unclassified Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 7 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


This came up during a recent BIND 10 team call:


There are several places where this type of information is stored:

  • src/lib/python/
  • in specific python scripts like
  • in some C++ files like auth/common.{h,cc}

Jinmei reports:

It's just a mess.  When you need to know the path, you'll need to
find multiple places.  When you need to add a new path, there can be
several ways and it's also possible that you invent yet another
place.  Also, there are some inconsistent cases like #1903.

So, what exactly I would envision is:

- introduce a unified place to define this information for all
  modules.  ideally this should be the only source for both Python and
- Python scripts and C++ sources refer to this place and use the
  information appropriately.
- Document the policy and how you add new things to the unified place.


Change History (3)

comment:1 Changed 7 years ago by shane

  • Milestone New Tasks deleted

comment:2 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:3 Changed 5 years ago by tomek

  • Resolution set to worksforme
  • Status changed from new to closed
  • Version set to git

All of those places are no longer in Kea code. Closing ticket.

Note: See TracTickets for help on using tickets.