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
** Changed in: holland-backup
Importance: Undecided => Medium
** Changed in: holland-backup
Assignee: (unassigned) => Andrew Garner (muzazzi)
** Changed in: holland-backup
Milestone: None => 1.0.6
--
You received this bug notification because you are a member of Holland
Discuss, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/671967
Title:
Handle log file errors more gracefully
Status in Holland Backup Framework:
Fix Committed
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'
_______________________________________________
Mailing list: https://launchpad.net/~holland-coredev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~holland-coredev
More help : https://help.launchpad.net/ListHelp
