<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/config/cloud.cfg.d/05_logging.cfg, branch rolling</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2020-06-12T19:48:53+00:00</updated>
<entry>
<title>Default to UTF-8 in /var/log/cloud-init.log (#427)</title>
<updated>2020-06-12T19:48:53+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2020-06-12T19:48:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=287bfca19d8ed386cd41dbc47753b7711ac1c848'/>
<id>urn:sha1:287bfca19d8ed386cd41dbc47753b7711ac1c848</id>
<content type='text'>
On a system with a non-utf8 default locale, the logger will silently
not log anything if the message contains an unsupported character.</content>
</entry>
<entry>
<title>Just use file logging by default</title>
<updated>2016-11-22T19:28:58+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>jxharlow@godaddy.com</email>
</author>
<published>2016-07-25T19:36:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=11b1aba4597379051e6b934e2b8f5a455e26ef14'/>
<id>urn:sha1:11b1aba4597379051e6b934e2b8f5a455e26ef14</id>
<content type='text'>
Instead of being dependent on the availability of syslog that
various distributions may not enable or configure correctly
or they do so via patches just use a known-to-work default
logging mechanism.  If distros want to change this, that
is fine, but at least the built-in one will work reliably.

LP: #1643990
</content>
</entry>
<entry>
<title>provide default 'output' setting to log to /var/log/cloud-init-output.log</title>
<updated>2014-01-14T18:18:14+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2014-01-14T18:18:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=08b50a6ea239f480493f202c563d788cabb92380'/>
<id>urn:sha1:08b50a6ea239f480493f202c563d788cabb92380</id>
<content type='text'>
This has been "best practice" for quite some time, and its a common
request of "where is the output of my user-data programs".

http://askubuntu.com/questions/345344/where-are-the-logs-for-my-user-data-script-cloud-init
</content>
</entry>
<entry>
<title>Add comments as to what the special reference sections mean in log_cfgs</title>
<updated>2012-06-19T00:30:21+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@yahoo-inc.com</email>
</author>
<published>2012-06-19T00:30:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=103e5fe784007a2ee3855031fd55d2470fa0d19c'/>
<id>urn:sha1:103e5fe784007a2ee3855031fd55d2470fa0d19c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>change from yaml+'#include' to yaml + config.d format for cloud.cfg</title>
<updated>2011-02-17T20:48:41+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2011-02-17T20:48:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=6fe51bb797810832de4301f85b5b3ca11630e108'/>
<id>urn:sha1:6fe51bb797810832de4301f85b5b3ca11630e108</id>
<content type='text'>
</content>
</entry>
</feed>
