BIND 10 #662: b10-auth wrongly falls back to default listen_on

[BIND 10 Development]

#662: b10-auth wrongly falls back to default listen_on
--------------------------------+---------------------------------
           Reporter:  jreed     |                      Owner:
               Type:  defect    |                     Status:  new
           Priority:  major     |                  Milestone:
          Component:  b10-auth  |                   Keywords:
          Sensitive:  0         |  Estimated Number of Hours:  0
Add Hours to Ticket:  0         |                  Billable?:  1
        Total Hours:  0         |                  Internal?:  0
--------------------------------+---------------------------------
 As I noted in #657, b10-auth now falls back to default listen_on (from
 spec?) if the b10-config.db version fails.


 {{{
 [bind10] BIND 10 started
 Setting listen addresses:
  0.0.0.0:53
  127.0.0.1:5300
 Initialize TCP server at 0.0.0.0:53
 Unable to set new address: Failed to initialize network servers:
 Permission denied
 [b10-auth] error: Server configuration failed: Failed to initialize
 network servers: Permission denied
 [b10-auth] Configuration channel established.
 [b10-auth] Xfrin session channel created.
 [b10-auth] Xfrin session channel established.
 [b10-auth] Statistics session channel created.
 [b10-auth] Statistics session channel established.
 Setting listen addresses:
  ::1:5300
  127.0.0.1:5300
 Initialize TCP server at ::1:5300
 Initialize UDP server at ::1:5300
 Initialize TCP server at 127.0.0.1:5300
 Initialize UDP server at 127.0.0.1:5300
 [b10-auth] Set statistics timer to 60 seconds
 [b10-auth] Data source database file:
 /usr/home/jreed/opt/bind10/var/bind10-devel/zone.sqlite3
 [b10-auth] Server started.

 }}}

 I think the previous behaviour was for it to exit. bind10 (boss) would
 restart and the failure would continue looping. I don't think that is good
 behaviour either.

 But using default values when a configuration is specifically defined is
 not correct.  It may not be noticed and it may break some policies or
 other software (which wanted to use those).

 Maybe this will be fixed in #657, but I open this ticket just in case.

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