Opened 7 years ago

Closed 7 years ago

#2181 closed defect (duplicate)

Store full paths in configuration when we use paths

Reported by: shane Owned by:
Priority: medium Milestone:
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 8 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


It might be nice to store full paths when we use them in our configuration. That way it would be obvious to an administrator if they accidentally ran the server in an incorrect directory and ended up configuring things against a bogus location, or also to prevent confusion if the server is run multiple times from different locations and gives different behavior.


Change History (4)

comment:1 Changed 7 years ago by vorner

There are two problems with this:

  • Who does the changing of relative to absolute paths? Bindctl? CmdCtl?? How do they know which paths to change or if a string is a path at all? Or specific checking routines?
  • Someone might want to have a relocable installation which would use relative paths on purpose.

comment:2 Changed 7 years ago by shane

Okay, perhaps a better approach would be to have a "run path" configuration option that specifies where BIND 10 goes via chdir() when running. It could be null to leave it wherever it was run from.

Also, it might be nice to have the boss log where it was starting from as an INFO-level message?

comment:3 Changed 7 years ago by shane

  • Milestone New Tasks deleted

comment:4 Changed 7 years ago by shane

  • Resolution set to duplicate
  • Status changed from new to closed

Ticket #2819 has a reasonable proposal that should address this issue. Resolving this as a "reverse duplicate". :)

Note: See TracTickets for help on using tickets.