BIND 10 #267: python log shouldn't die with OSError

[BIND 10 Development]

#267: python log shouldn't die with OSError
---------------------+------------------------------------------------------
 Reporter:  jinmei   |        Owner:  zzchen_pku                 
     Type:  defect   |       Status:  reviewing                  
 Priority:  major    |    Milestone:  06. 4th Incremental Release
Component:  logging  |   Resolution:                             
 Keywords:           |    Sensitive:  0                          
---------------------+------------------------------------------------------

Comment(by zzchen_pku):

 Replying to [comment:5 jinmei]:
 > One more thing: while I believe it's better to keep running even if a
 systm level error (file is non writable, etc) occurs with logging, it
 would also be nice if we could report the error in some way.  In
 particular, if stderr is writable, reporting it there at initialization
 time would be helpful (an error that happens in writing logs may not be
 effectively reportable, but I think we can live with that).
 >
 > Dying due to an error for an optional feature isn't good, but silently
 ignoring errors is not good either.

 Because I think most users will not care about errors in the logging
 system, they are more interested in application errors.
 Maybe you are right, we could report the error to stderr.

-- 
Ticket URL: <http://bind10.isc.org/ticket/267#comment:7>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development