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
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jinmei


Comment:

 Hello

 Replying to [comment:4 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?

 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.

 Anyway, I think the environment variable hack is reasonable. The variable
 is
 only between boss and the started modules. It has no effect if set from
 outside
 and passed to boss.

 > 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.

 I don't know if a config file is a good place here. We need to know the
 place
 of lock file before we read the config, otherwise we'll get race
 conditions. Or
 maybe not, but we would have to be very careful. Anyway, we need a way to
 start
 as a user if we don't have a write permission to the default path, so
 config
 file wouldn't help here. And having a path to finding configuration in a
 configuration file is kind of useless.

 But yes, we need to solve it somehow. But I don't think we want to do it
 in
 this ticket.

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