if a logged message fails, fallback to logging to stdout

This most commonly occurs if a user-data script does '/sbin/poweroff'
where syslog was being used.  Once poweroff is invoked, syslog gets killed
and logging would start to show stack traces.

This generally tries to continue working instead, but log to stderr.

1 files changed, 2 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index aca34d6e..c5dcd418 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,6 @@
 0.7.0:
+ - catch signals and exit rather than stack tracing
+ - if logging fails, enable a fallback logger by patching the logging module
  - do not 'start networking' in cloud-init-nonet, but add
    cloud-init-container job that runs only if in container and emits
    net-device-added (LP: #1031065)