summaryrefslogtreecommitdiff
path: root/doc/sources/smartos/README.rst
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2013-09-25 14:52:55 -0400
committerScott Moser <smoser@ubuntu.com>2013-09-25 14:52:55 -0400
commit9e5fd8410033bce66e4eaa2b51e29801c8327519 (patch)
tree9bfd20e85b4d6cf33ea3dad754aa9e35d42a020f /doc/sources/smartos/README.rst
parent3bebad68b627595652eabc9e7222b69197180622 (diff)
parentf0e1bf38a2b943d27c8fe20724799b2e552e7adc (diff)
downloadvyos-cloud-init-9e5fd8410033bce66e4eaa2b51e29801c8327519.tar.gz
vyos-cloud-init-9e5fd8410033bce66e4eaa2b51e29801c8327519.zip
multi_log: only write to /dev/console if it exists.
Some containers lack /dev/console, so when multi_log attempts to open that device and write to it directly things can start going haywire. Here we address this problem by sending console-bound output to stdout and letting init take care of getting it to the console instead. We already configure upstart with "console output", so we need only change systemd to use "journal+console". The one reason that 'console output' might not be sufficient is if the user redirected output with 'output'. Ie: output: init: "> /var/log/my-cloud-init.log" Would then mean all output would go there, and anything that *needed* to go to the console (and was explicitly using multi_log for that purpose) would not get there.
Diffstat (limited to 'doc/sources/smartos/README.rst')
0 files changed, 0 insertions, 0 deletions