BIND 10 #2557: lockfile should use --data-path

[BIND 10 Development]

#2557: lockfile should use --data-path
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |  jinmei
            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):

 Replying to [comment:6 vorner]:

 > > Considering this is for an optional case, should we really solve
 > > this particular topic separately, especially by introducing yet
 > > another hack of environment variable?
 >
 > Well, the ticket is for solving this problem, not for solving (much
 larger)
 > general problem. And it is in the sprint… But I'll write an email to the
 ML
 > asking for proposed solutions.

 I'm not arguing for solving the larger problem in this ticket.  I
 wondered whether it makes more sense to hold or cancel (as "won't
 fix") this task until we clarify the bigger issue.

 If this is a critical defect that affects many users, I see the need
 for an urgent care fix.  But it doesn't seem to be so - "-p" wouldn't
 be used normally, and as already suggested in the ticket description,
 there already seems to be a workaround.

 We could fix this particular issue in some way anyway and then
 consider the bigger issue.  But I'd be careful about that approach,
 because any new code introduced in the master branch will work as a
 precedent that will hinder higher level work.

 But it may be only me...so my suggestion is to get the sense of the
 team on if we really want/need to fix this particular issue right now,
 in any workable way.  If that's the consensus I'll follow it.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2557#comment:7>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development