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

[BIND 10 Development]

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

 * owner:  vorner => UnAssigned
 * status:  accepted => reviewing


Comment:

 I used a private environment variable to pass it around, but the user
 shouldn't
 be in contact with it. It seemed the easiest way around, the other
 possibility
 would be passing options around to each process, but each process would
 have to
 explicitly handle it, making it harder to create new ones and providing
 many
 duplicate pieces of code.

 But I didn't come up with a way to test it easily. I did confirm manually
 ‒ I
 run once without the `-p`, and it created it in the default place. When I
 set
 the `-p` argument, the lock file was at that place (and not in the default
 one).

 Proposed changelog:
 {{{
 The command line parameter of boss `-p` now influences the place
 of logging lock file. This solves a problem when the default path
 wasn't accessible by the user running bind10.
 }}}

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