<?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 on: Thoughts on reliable syslog</title>
	<atom:link href="http://mschuette.name/wp/2008/03/31/thoughts-on-reliable-syslog/feed/" rel="self" type="application/rss+xml" />
	<link>http://mschuette.name/wp/2008/03/31/thoughts-on-reliable-syslog/</link>
	<description>枕草子</description>
	<lastBuildDate>Tue, 08 Jun 2010 21:01:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Rainer Gerhards</title>
		<link>http://mschuette.name/wp/2008/03/31/thoughts-on-reliable-syslog/comment-page-1/#comment-79</link>
		<dc:creator>Rainer Gerhards</dc:creator>
		<pubDate>Tue, 22 Apr 2008 12:44:08 +0000</pubDate>
		<guid isPermaLink="false">http://mschuette.name/wp/2008/03/31/thoughts-on-reliable-syslog/#comment-79</guid>
		<description>Hi, this is a a really good summary of the problems encountered with reliable syslog. You just missed one thing, I think: a buffer must not necessarily exist only in main memory. When the in-core buffer runs out of space, you may also use a disk-based buffer, which offers much more capacity. Of course, even the largest disk-based buffer may be exhausted at some point, where one needs to resort to other strategies. But a disk-based buffer is an excellent solution for temporary (but lengthy) receiver outages. As as side-note, rsyslog has implemented all three buffer handling options. If you are interested, you may want to have a look at it&#039;s queue module description (yes, this proves the point of being a produce-consumer problem ;)):

&lt;a href=&quot;http://www.rsyslog.com/doc-queues.html&quot; rel=&quot;nofollow&quot;&gt;http://www.rsyslog.com/doc-queues.html&lt;/a&gt;

Rainer</description>
		<content:encoded><![CDATA[<p>Hi, this is a a really good summary of the problems encountered with reliable syslog. You just missed one thing, I think: a buffer must not necessarily exist only in main memory. When the in-core buffer runs out of space, you may also use a disk-based buffer, which offers much more capacity. Of course, even the largest disk-based buffer may be exhausted at some point, where one needs to resort to other strategies. But a disk-based buffer is an excellent solution for temporary (but lengthy) receiver outages. As as side-note, rsyslog has implemented all three buffer handling options. If you are interested, you may want to have a look at it&#8217;s queue module description (yes, this proves the point of being a produce-consumer problem ;)):</p>
<p><a href="http://www.rsyslog.com/doc-queues.html" rel="nofollow">http://www.rsyslog.com/doc-queues.html</a></p>
<p>Rainer</p>
]]></content:encoded>
	</item>
</channel>
</rss>
