BIND 10 #2557: lockfile should use --data-path
BIND 10 Development
do-not-reply at isc.org
Thu Dec 27 23:03:05 UTC 2012
#2557: lockfile should use --data-path
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | UnAssigned
Priority: medium | Status:
Component: logging | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20130108
Sub-Project: Core | Resolution:
Estimated Difficulty: 3 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
Considering this is for an optional case, should we really solve
this particular topic separately, especially by introducing yet
another hack of environment variable?
I start feeling that it might be a good timing to clarify the
convoluted setup for various paths: what kind of concept we need, and
how we manage them (in config file, command line arg, and/or
environment variable) with which policy, and document these. If we
can solve this particular topic on top of that clarification more
cleanly, that would be the best; if we still need some kind of hack,
we can at least introduce it according to the documented policy.
And I think it's better if we can clarify it before the non-beta
release as it will be more difficult to correct the things once more
people rely on these existing hacks.
--
Ticket URL: <http://bind10.isc.org/ticket/2557#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list