<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Linux ulimit memory enforcement oddity</title>
	<atom:link href="http://www.csamuel.org/2007/11/30/linux-ulimit-memory-enforcement-oddity/feed" rel="self" type="application/rss+xml" />
	<link>http://www.csamuel.org/2007/11/30/linux-ulimit-memory-enforcement-oddity</link>
	<description>The Thoughts and Feelings of a Melbourne Person</description>
	<lastBuildDate>Fri, 05 Mar 2010 20:34:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Janni</title>
		<link>http://www.csamuel.org/2007/11/30/linux-ulimit-memory-enforcement-oddity/comment-page-1#comment-18853</link>
		<dc:creator>Janni</dc:creator>
		<pubDate>Tue, 18 Mar 2008 23:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/2007/11/30/linux-ulimit-memory-enforcement-oddity/#comment-18853</guid>
		<description>Thanks Chris for sharing this information with us.</description>
		<content:encoded><![CDATA[<p>Thanks Chris for sharing this information with us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan Sokolow&#8217;s Blog &#187; Setting memory limits on Linux</title>
		<link>http://www.csamuel.org/2007/11/30/linux-ulimit-memory-enforcement-oddity/comment-page-1#comment-18428</link>
		<dc:creator>Stephan Sokolow&#8217;s Blog &#187; Setting memory limits on Linux</dc:creator>
		<pubDate>Tue, 11 Mar 2008 02:58:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.csamuel.org/2007/11/30/linux-ulimit-memory-enforcement-oddity/#comment-18428</guid>
		<description>[...] might not be aware of this, but since some time during the glibc 2.3 era, Linux apparently doesn&#8217;t enforce the RSS memory limit. (ulimit -m) My tests seem to confirm [...]</description>
		<content:encoded><![CDATA[<p>[...] might not be aware of this, but since some time during the glibc 2.3 era, Linux apparently doesn&#8217;t enforce the RSS memory limit. (ulimit -m) My tests seem to confirm [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
