Handle log file errors more gracefully

Bug #671967 reported by Andrew Garner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
holland-backup
Fix Released
Medium
Andrew Garner

Bug Description

If the log file can't be written (maybe the directory is missing or we don't have permissions, etc.) holland should handle that gracefully - either aborting or just continuing on with a log file.

File "/usr/lib/python2.4/site-packages/holland/core/backports/logging/__init__.py", line 749, in __init__
stream = codecs.open(filename, mode, encoding)
File "/usr/lib64/python2.4/codecs.py", line 666, in open
file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 2] No such file or directory: '/var/log/holland/holland.log'

Revision history for this message
Andrew Garner (muzazzi) wrote :

IOErrors when opening log files are now treated as non-fatal and file logging will simply be skipped.

Changed in holland-backup:
status: New → Fix Committed
importance: Undecided → Medium
assignee: nobody → Andrew Garner (muzazzi)
milestone: none → 1.0.6
Andrew Garner (muzazzi)
Changed in holland-backup:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.