<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Raskas' blog &#187; bug</title>
	<atom:link href="http://www.raskas.be/blog/tag/bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.raskas.be/blog</link>
	<description>Everything is possible... You only have to find out how.</description>
	<lastBuildDate>Wed, 22 Jun 2011 15:14:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>syslog-ng bug</title>
		<link>http://www.raskas.be/blog/2009/03/19/syslog-ng-bug/</link>
		<comments>http://www.raskas.be/blog/2009/03/19/syslog-ng-bug/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 11:49:57 +0000</pubDate>
		<dc:creator>Johan Huysmans</dc:creator>
				<category><![CDATA[Linux SysAdmin]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[syslog-ng]]></category>

		<guid isPermaLink="false">http://www.raskas.be/blog/?p=91</guid>
		<description><![CDATA[Today I stumpled upon a syslog-ng bug.
We are using syslog-ng-2.1.3 on one of our machines which sends part of his messages over UDP to 2 syslog machines. On some days we noticed that syslog-ng and some other services are stopped. Restarting syslog-ng showed us that they were killed by the OOM-killer.
I directly suspected the java [...]]]></description>
			<content:encoded><![CDATA[<p>Today I stumpled upon a syslog-ng bug.</p>
<p>We are using syslog-ng-2.1.3 on one of our machines which sends part of his messages over UDP to 2 syslog machines. On some days we noticed that syslog-ng and some other services are stopped. Restarting syslog-ng showed us that they were killed by the OOM-killer.<br />
I directly suspected the java process that was also running on that machine.</p>
<p>After googling around I found this syslog-ng bug: <a href="https://bugzilla.balabit.com/show_bug.cgi?id=39" target="_blank">https://bugzilla.balabit.com/show_bug.cgi?id=39</a></p>
<p>And indeed, we had the same problem. This is how I could reproduce it:</p>
<ul>
<li>Stop the syslog service (on the host which receives the messages)</li>
<li>Restart syslog-ng</li>
<li>Watch the memory usage of syslog-ng growing until it starts swapping and triggers the OOM-killer</li>
</ul>
<p>Luckily this bug is already solved, and by upgrading to syslog-ng-2.1.4 the problem is fixed.</p>
<p>CentOS doesn&#8217;t provide the rpm packages of syslog-ng, <a href="http://www.silfreed.net/" target="_blank">silfreed.net</a> does: <a href="http://www.silfreed.net/download/repo/" target="_blank">http://www.silfreed.net/download/repo/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.raskas.be/blog/2009/03/19/syslog-ng-bug/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Input/Output redirection, appending</title>
		<link>http://www.raskas.be/blog/2008/08/15/inputoutput-redirection-appending/</link>
		<comments>http://www.raskas.be/blog/2008/08/15/inputoutput-redirection-appending/#comments</comments>
		<pubDate>Fri, 15 Aug 2008 13:58:18 +0000</pubDate>
		<dc:creator>Johan Huysmans</dc:creator>
				<category><![CDATA[Linux SysAdmin]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[bug]]></category>

		<guid isPermaLink="false">http://www.raskas.be/blog/?p=85</guid>
		<description><![CDATA[In a previous post I wrote about output redirection of STDOUT, STDERR and both to a file. Off course you can do the same to append to an existing file:

ls &#62;&#62; output.txt
ls 2&#62;&#62; error.txt

If you try this with &#38;&#62;&#62; you will receive a bash syntax error:

ls &#38;&#62;&#62; output_and_error.txt
bash: syntax error near unexpected token `&#62;'

How come [...]]]></description>
			<content:encoded><![CDATA[<p>In <a href="http://www.raskas.be/blog/2007/02/26/inputoutput-redirection/" target="_blank">a previous post</a> I wrote about output redirection of STDOUT, STDERR and both to a file. Off course you can do the same to append to an existing file:<br />
<code><br />
ls &gt;&gt; output.txt<br />
ls 2&gt;&gt; error.txt<br />
</code><br />
If you try this with &amp;&gt;&gt; you will receive a bash syntax error:<br />
<code><br />
ls &amp;&gt;&gt; output_and_error.txt<br />
bash: syntax error near unexpected token `&gt;'<br />
</code></p>
<p>How come appending of both STDOUT and STDERR to a file does not work this way? Is this a bug in bash?<br />
Yes, I know I can use the following, but I prefer the &amp;&gt;&gt;:<code><br />
ls 1>> output_and_error.txt 2>&#038;1<br />
</code></p>
<p>And how come I can&#8217;t find a bugzilla for bash?<br />
Yes, I know I can use the command bashbug to send a mail to a mailinglist, but this is not the same as bugzilla.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.raskas.be/blog/2008/08/15/inputoutput-redirection-appending/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

