BIND 10 #109: bind10 loop restarting b10-auth even if can't bind socket

[BIND 10 Development]

#109: bind10 loop restarting b10-auth even if can't bind socket
----------------------+-----------------------------------------------------
 Reporter:  jreed     |        Owner:  jreed                      
     Type:  defect    |       Status:  reviewing                  
 Priority:  minor     |    Milestone:  04. 2nd Incremental Release
Component:  b10-auth  |   Resolution:                             
 Keywords:            |    Sensitive:  0                          
----------------------+-----------------------------------------------------

Comment(by jreed):

 Replying to [comment:9 each]:
 > > I forgot to mention that this was with boost-system so using the BOOST
 ASIO. I am compiling the branch now. As for the patch it looked to be only
 cosmetic -- but looks great!
 >
 > Thanks.  I can merge if you think it's ready, but I'd like your input on
 a few things first...
 >
 > Is there a problem with the restart-loop behavior mentioned in the
 ticket description?  I'm inclined to think it's the right thing to do, as
 long as b10-auth is being clear about what's going wrong.


 Yes it is probably correct to loop, not sure how fast it should attempt to
 restart. But the error message must be clear. The error message as I see
 it is clear but doesn't indicate what component sent the message. So
 running BIND 10 you don't know which module prints the error.

 > Also wondering if I should add more "[b10-auth]" prefixes in AuthSrv.
 (There are some "[AuthSrv]" prefixes in there already, and this seems
 wrong to me; I think it's more useful to tell people which program had
 trouble than which library function it was calling at the time.)

 I agree it is more useful to know which program. Later when we add a
 debugging framework we can improve this.

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