BIND 10 #151: XfroutClient socket location and removal

BIND 10 Development do-not-reply at isc.org
Wed Jun 2 10:51:19 UTC 2010


#151: XfroutClient socket location and removal
--------------------+-------------------------------------------------------
 Reporter:  jreed   |        Owner:  zhanglikun                 
     Type:  defect  |       Status:  assigned                   
 Priority:  major   |    Milestone:  05. 3rd Incremental Release
Component:  xfrout  |   Resolution:                             
 Keywords:          |    Sensitive:  0                          
--------------------+-------------------------------------------------------
Changes (by shane):

  * owner:  shentingting => zhanglikun


Comment:

 English correction:

 "it becauses one other xfrout" -> "because another xfrout"

 Comment typo:

 "esle" -> "else"

 Comment correction:

 "should be removed" -> "will be removed"

 It's not very important, but I would move the error message out of the
 `_sock_file_in_use()` function and into the `__init()__` function before
 the `sys.exit()` call. This will make it easier to re-use the code if we
 want to have a similar technique elsewhere.

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


More information about the bind10-tickets mailing list