<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for rsyslog</title>
	<atom:link href="http://www.rsyslog.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rsyslog.com</link>
	<description>rsyslog, the enhanced syslogd</description>
	<lastBuildDate>Tue, 31 Jan 2012 16:43:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Storing Messages from a Remote System into a specific File by rgerhards</title>
		<link>http://www.rsyslog.com/storing-messages-from-a-remote-system-into-a-specific-file/comment-page-1/#comment-239</link>
		<dc:creator>rgerhards</dc:creator>
		<pubDate>Tue, 31 Jan 2012 16:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=166#comment-239</guid>
		<description>Did you use different types of quote characters? At least in the comment it looks so.</description>
		<content:encoded><![CDATA[<p>Did you use different types of quote characters? At least in the comment it looks so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Storing Messages from a Remote System into a specific File by Stefan</title>
		<link>http://www.rsyslog.com/storing-messages-from-a-remote-system-into-a-specific-file/comment-page-1/#comment-238</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Sun, 29 Jan 2012 18:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=166#comment-238</guid>
		<description>This syntax does not work with rsyslog 5.8.6 that ships with the widely used Debian Squeeze distrobution. 

# provides TCP syslog reception
$ModLoad imtcp
$InputTCPServerRun 514

$template HostBasedLog,&quot;/var/log/%HOSTNAME%.log&quot;
if $fromhost-ip isequal &#039;192.168.22.1&#039; then -?HostBasedLog
&amp; ~
if $fromhost-ip isequal &#039;192.168.22.2&#039; then -?HostBasedLog
&amp; ~

Causes syntax errors on those two lines &quot;syntax error in expression&quot; 

the last error occured in /etc/rsyslog.conf, line 26:&quot;if $fromhost-ip isequal &#039;192.168.22.2&#039; then -?HostBasedLog&quot;</description>
		<content:encoded><![CDATA[<p>This syntax does not work with rsyslog 5.8.6 that ships with the widely used Debian Squeeze distrobution. </p>
<p># provides TCP syslog reception<br />
$ModLoad imtcp<br />
$InputTCPServerRun 514</p>
<p>$template HostBasedLog,&#8221;/var/log/%HOSTNAME%.log&#8221;<br />
if $fromhost-ip isequal &#8216;192.168.22.1&#8242; then -?HostBasedLog<br />
&amp; ~<br />
if $fromhost-ip isequal &#8216;192.168.22.2&#8242; then -?HostBasedLog<br />
&amp; ~</p>
<p>Causes syntax errors on those two lines &#8220;syntax error in expression&#8221; </p>
<p>the last error occured in /etc/rsyslog.conf, line 26:&#8221;if $fromhost-ip isequal &#8216;192.168.22.2&#8242; then -?HostBasedLog&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using a different log Format for all Files by rgerhards</title>
		<link>http://www.rsyslog.com/using-a-different-log-format-for-all-files/comment-page-1/#comment-233</link>
		<dc:creator>rgerhards</dc:creator>
		<pubDate>Wed, 18 Jan 2012 11:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=164#comment-233</guid>
		<description>Well, how about doing some of that work yourself? I am far from opposing doc contributions. I know the doc is not well, but there is so much to do. The open source way is collaboration, not a single person doing all work ;)</description>
		<content:encoded><![CDATA[<p>Well, how about doing some of that work yourself? I am far from opposing doc contributions. I know the doc is not well, but there is so much to do. The open source way is collaboration, not a single person doing all work ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using a different log Format for all Files by new user</title>
		<link>http://www.rsyslog.com/using-a-different-log-format-for-all-files/comment-page-1/#comment-231</link>
		<dc:creator>new user</dc:creator>
		<pubDate>Sun, 15 Jan 2012 18:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=164#comment-231</guid>
		<description>PS - the cross reference is for:

http://rsyslog.com/doc/rsyslog_conf_templates.html


This describes the format. I think we can just put them in the main config file, but again, no simple instructions exist.

For example, there is no explanation of the standard debug template output.

I just want to see facility and level displayed on each line. I found the syntax from a ~version 1.7 document, but maybe it will not work. 

I think the software is very good, but the documentation is full but unstructured perhaps.
I know it is hard to find time for such cleanup. danke!</description>
		<content:encoded><![CDATA[<p>PS &#8211; the cross reference is for:</p>
<p><a href="http://rsyslog.com/doc/rsyslog_conf_templates.html" rel="nofollow">http://rsyslog.com/doc/rsyslog_conf_templates.html</a></p>
<p>This describes the format. I think we can just put them in the main config file, but again, no simple instructions exist.</p>
<p>For example, there is no explanation of the standard debug template output.</p>
<p>I just want to see facility and level displayed on each line. I found the syntax from a ~version 1.7 document, but maybe it will not work. </p>
<p>I think the software is very good, but the documentation is full but unstructured perhaps.<br />
I know it is hard to find time for such cleanup. danke!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using a different log Format for all Files by new user</title>
		<link>http://www.rsyslog.com/using-a-different-log-format-for-all-files/comment-page-1/#comment-230</link>
		<dc:creator>new user</dc:creator>
		<pubDate>Sun, 15 Jan 2012 18:32:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=164#comment-230</guid>
		<description>And...

&quot;But getting into the detail of all of that is beyond the scope of this cookbook-style book.&quot;

Very funny! Perhaps you have read a cookbook where you need some spices or ingredients, but the author just assumes that everyone knows what is &quot;frimminjamzen&quot; and tells you you need 100g, but you don&#039;t know what this is. A little google and you know that it is anchovies. This situation is not so bad... it is just a translation.

Now imagine that the same author tells you to &quot;arnzarnz&quot; the potatoes and leeks, but only his family uses this word. Now google becomes less useful. maybe you will be lucky and another family uses it, enough that a search engine can help you eventually discover that it means to dice the mixture into 1cm cubes.
The situation is worse, but not hopeless.

Finally, imagine that a software author tells us how to apply a special to a system logger. The author does not tell us how to  make the special format template, or where to put it so that the software will find it. He simply tells us we can use one and give it whatever name we like...

It is like the spanish recipes for a love potion... one needs a unicorn horn and a tooth from a chimera, although everything else is easy to find. The recipes NEVER explain where one can FIND a unicorn (yes, yes, we know that you must have a virgin, but then what?) let alone find the &quot;unicorn horn&quot; or where one can find the tooth of a chimera.

In our case, we are missing &quot;see this document or url for more info&quot; or &quot;the filepath to the templates is xxx/xxxx&quot; or &quot;here is an example 

There is nothing here explaining:

- where is the default template specified?

- where can one find the format for the template?</description>
		<content:encoded><![CDATA[<p>And&#8230;</p>
<p>&#8220;But getting into the detail of all of that is beyond the scope of this cookbook-style book.&#8221;</p>
<p>Very funny! Perhaps you have read a cookbook where you need some spices or ingredients, but the author just assumes that everyone knows what is &#8220;frimminjamzen&#8221; and tells you you need 100g, but you don&#8217;t know what this is. A little google and you know that it is anchovies. This situation is not so bad&#8230; it is just a translation.</p>
<p>Now imagine that the same author tells you to &#8220;arnzarnz&#8221; the potatoes and leeks, but only his family uses this word. Now google becomes less useful. maybe you will be lucky and another family uses it, enough that a search engine can help you eventually discover that it means to dice the mixture into 1cm cubes.<br />
The situation is worse, but not hopeless.</p>
<p>Finally, imagine that a software author tells us how to apply a special to a system logger. The author does not tell us how to  make the special format template, or where to put it so that the software will find it. He simply tells us we can use one and give it whatever name we like&#8230;</p>
<p>It is like the spanish recipes for a love potion&#8230; one needs a unicorn horn and a tooth from a chimera, although everything else is easy to find. The recipes NEVER explain where one can FIND a unicorn (yes, yes, we know that you must have a virgin, but then what?) let alone find the &#8220;unicorn horn&#8221; or where one can find the tooth of a chimera.</p>
<p>In our case, we are missing &#8220;see this document or url for more info&#8221; or &#8220;the filepath to the templates is xxx/xxxx&#8221; or &#8220;here is an example </p>
<p>There is nothing here explaining:</p>
<p>- where is the default template specified?</p>
<p>- where can one find the format for the template?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to use debug on demand? by new user</title>
		<link>http://www.rsyslog.com/how-to-use-debug-on-demand/comment-page-1/#comment-229</link>
		<dc:creator>new user</dc:creator>
		<pubDate>Sun, 15 Jan 2012 17:58:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=186#comment-229</guid>
		<description>How I wish decent intermediate background tutorials were available for rsyslogd. Something for configuration to bridge the gap between &quot;make install&quot; and &quot;here&#039;s how to log to sql&quot;.

After ~15 years, linux docs are still being written assuming that one already understands everything but just needs some notes.

Nothing like 3 days of google and being unable to precisely identify which facility and log-level a message came from, or worse yet, unable to find simple building block examples of &quot;This conf file rule results in the following output lines/actions/etc&quot;.  I only find snippets of rules all glommed into one to provide grammar examples... but with no &quot;do this--&gt;get this&quot; examples of output for it.
 
I suppose I should write something up, since I&#039;m treading that long stone-covered road myself.</description>
		<content:encoded><![CDATA[<p>How I wish decent intermediate background tutorials were available for rsyslogd. Something for configuration to bridge the gap between &#8220;make install&#8221; and &#8220;here&#8217;s how to log to sql&#8221;.</p>
<p>After ~15 years, linux docs are still being written assuming that one already understands everything but just needs some notes.</p>
<p>Nothing like 3 days of google and being unable to precisely identify which facility and log-level a message came from, or worse yet, unable to find simple building block examples of &#8220;This conf file rule results in the following output lines/actions/etc&#8221;.  I only find snippets of rules all glommed into one to provide grammar examples&#8230; but with no &#8220;do this&#8211;&gt;get this&#8221; examples of output for it.</p>
<p>I suppose I should write something up, since I&#8217;m treading that long stone-covered road myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Storing and forwarding remote messages by rgerhards</title>
		<link>http://www.rsyslog.com/storing-and-forwarding-remote-messages/comment-page-1/#comment-228</link>
		<dc:creator>rgerhards</dc:creator>
		<pubDate>Mon, 09 Jan 2012 11:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=356#comment-228</guid>
		<description>It can be used to suppress syncing to files, if that is activated. By default, sync is disabled, so &quot;-&quot; has no meaning in that setup. It is mostly a left-over from previous versions. Check &quot;output file syncing&quot; in this doc for more details: http://rsyslog.com/doc/v3compatibility.html</description>
		<content:encoded><![CDATA[<p>It can be used to suppress syncing to files, if that is activated. By default, sync is disabled, so &#8220;-&#8221; has no meaning in that setup. It is mostly a left-over from previous versions. Check &#8220;output file syncing&#8221; in this doc for more details: <a href="http://rsyslog.com/doc/v3compatibility.html" rel="nofollow">http://rsyslog.com/doc/v3compatibility.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Storing Messages from a Remote System into a specific File by Steve</title>
		<link>http://www.rsyslog.com/storing-messages-from-a-remote-system-into-a-specific-file/comment-page-1/#comment-227</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 05 Jan 2012 20:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=166#comment-227</guid>
		<description>http://rsyslog.com/config-snippets/the-recipies/more-complex-scenarios/ shows a different method of routing remote syslog message to a separate file by binding the TCP and UDP ports to a ruleset.  Which method is preferred?  In my specific scenario, I want to log messages from a piece of test equipment to a separate file to keep them from contaminating my workstations legitimate log files.  My workstation did not previously have TCP or UDP on, and won&#039;t receive any &quot;real&quot; syslog message over the network.</description>
		<content:encoded><![CDATA[<p><a href="http://rsyslog.com/config-snippets/the-recipies/more-complex-scenarios/" rel="nofollow">http://rsyslog.com/config-snippets/the-recipies/more-complex-scenarios/</a> shows a different method of routing remote syslog message to a separate file by binding the TCP and UDP ports to a ruleset.  Which method is preferred?  In my specific scenario, I want to log messages from a piece of test equipment to a separate file to keep them from contaminating my workstations legitimate log files.  My workstation did not previously have TCP or UDP on, and won&#8217;t receive any &#8220;real&#8221; syslog message over the network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Storing and forwarding remote messages by Dame</title>
		<link>http://www.rsyslog.com/storing-and-forwarding-remote-messages/comment-page-1/#comment-226</link>
		<dc:creator>Dame</dc:creator>
		<pubDate>Wed, 04 Jan 2012 17:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=356#comment-226</guid>
		<description>Hi

I have a question and could not find it in docu.
What does the &quot;-&quot; sign mean before the file name?
For example:
-/var/log/maillog

Thx for help.</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>I have a question and could not find it in docu.<br />
What does the &#8220;-&#8221; sign mean before the file name?<br />
For example:<br />
-/var/log/maillog</p>
<p>Thx for help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What are &#8220;Trusted Properties&#8221;? by rgerhards</title>
		<link>http://www.rsyslog.com/what-are-trusted-properties/comment-page-1/#comment-222</link>
		<dc:creator>rgerhards</dc:creator>
		<pubDate>Tue, 13 Dec 2011 12:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.rsyslog.com/?p=526#comment-222</guid>
		<description>@Tim B: again, sorry for the late reply. I like your idea about the glibc change, but am somewhat doubtful if Ulrich will do that. One possibility I see is that CEE syslog encoding could be used inside the syslog API. Assuming that a decent logging system needs to support CEE in the medium term, syslogd&#039;s will need parsing support for that anyways. So it would be very easy to parse that same format off the  system log socket. Actually, that was what I originally was looking into, and waiting that CEE would be final released (1.0) is due.</description>
		<content:encoded><![CDATA[<p>@Tim B: again, sorry for the late reply. I like your idea about the glibc change, but am somewhat doubtful if Ulrich will do that. One possibility I see is that CEE syslog encoding could be used inside the syslog API. Assuming that a decent logging system needs to support CEE in the medium term, syslogd&#8217;s will need parsing support for that anyways. So it would be very easy to parse that same format off the  system log socket. Actually, that was what I originally was looking into, and waiting that CEE would be final released (1.0) is due.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

