<?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"
	>
<channel>
	<title>Comments on: How to enlarge Coredump Size and File Descriptor Limitations</title>
	<atom:link href="http://weblog.pigfoot.org/pigfoot/2006/08/25/how-to-enlarge-coredump-size-and-file-descriptor-limitations/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblog.pigfoot.org/pigfoot/2006/08/25/how-to-enlarge-coredump-size-and-file-descriptor-limitations/</link>
	<description>We should forget about small efficiencies -- Donald Knuth</description>
	<pubDate>Tue, 02 Dec 2008 03:11:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: How to force setuid program to make a core dump?</title>
		<link>http://weblog.pigfoot.org/pigfoot/2006/08/25/how-to-enlarge-coredump-size-and-file-descriptor-limitations/#comment-15753</link>
		<dc:creator>How to force setuid program to make a core dump?</dc:creator>
		<pubDate>Sun, 09 Sep 2007 17:20:43 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.pigfoot.org/pigfoot/2006/08/25/how-to-enlarge-coredump-size-and-file-descriptor-limitations/#comment-15753</guid>
		<description>[...] Core dump 的方法就是利用 bash built-in 的 ulimit 指令. 我去年這篇 How to enlarge Coredump Size and File Descriptor Limitations [...]</description>
		<content:encoded><![CDATA[<p>[...] Core dump 的方法就是利用 bash built-in 的 ulimit 指令. 我去年這篇 How to enlarge Coredump Size and File Descriptor Limitations [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pigfoot</title>
		<link>http://weblog.pigfoot.org/pigfoot/2006/08/25/how-to-enlarge-coredump-size-and-file-descriptor-limitations/#comment-5158</link>
		<dc:creator>pigfoot</dc:creator>
		<pubDate>Fri, 15 Sep 2006 09:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.pigfoot.org/pigfoot/2006/08/25/how-to-enlarge-coredump-size-and-file-descriptor-limitations/#comment-5158</guid>
		<description>Yes.

In fact, if you study the source of su (&lt;a rel="nofollow" target="_blank" href="http://www.linuxfromscratch.org/blfs/view/svn/postlfs/shadow.html" rel="nofollow"&gt;shadow&lt;/a&gt; 4.0.15l), you can find the reason: it will be forked a privilege process and previous process will wait this privilege process terminated.

In other words, any environment variables changed in privilege process will not reflect on non-privilege process.</description>
		<content:encoded><![CDATA[<p>Yes.</p>
<p>In fact, if you study the source of su (<a rel="nofollow" target="_blank" href="http://www.linuxfromscratch.org/blfs/view/svn/postlfs/shadow.html" rel="nofollow">shadow</a> 4.0.15l), you can find the reason: it will be forked a privilege process and previous process will wait this privilege process terminated.</p>
<p>In other words, any environment variables changed in privilege process will not reflect on non-privilege process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kmwang</title>
		<link>http://weblog.pigfoot.org/pigfoot/2006/08/25/how-to-enlarge-coredump-size-and-file-descriptor-limitations/#comment-4242</link>
		<dc:creator>kmwang</dc:creator>
		<pubDate>Fri, 25 Aug 2006 09:56:59 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.pigfoot.org/pigfoot/2006/08/25/how-to-enlarge-coredump-size-and-file-descriptor-limitations/#comment-4242</guid>
		<description>As you showed, changing maxfd is a privileged operation. So I think losing maxfd setting is a reasonable system behavior. :P</description>
		<content:encoded><![CDATA[<p>As you showed, changing maxfd is a privileged operation. So I think losing maxfd setting is a reasonable system behavior. :P</p>
]]></content:encoded>
	</item>
</channel>
</rss>
