BIND 10 #2068: a convenient interface to choose lock policy for logging

[BIND 10 Development]

#2068: a convenient interface to choose lock policy for logging
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  logging       |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 It's annoying that interprocess file lock is required by default.
 for example, b10-dbutil will fail if the lock file can be created
 only by a specific group of users.

 There should be some easy way for each application can specify which
 lock policy (at least including "none") should be used for logging
 at the initialization time.  We also need a python interface for that.

 On top of that, I suggest we use the "none" policy by default, and
 require explicit setting for those who need interprocess locking.
 The only benefit the lock provides is to avoid mixed logging output
 by multiple processes.  While it's nice, but not crucial for the
 system to work.  It's much, much worse that some tool cannot even
 start due to the failure of getting access to the unnecessary lock
 file.  The default should prevent that from happening.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2068>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development