<?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: Attempting to unwind the tangled web of pid file creation.</title>
	<atom:link href="http://ebergen.net/wordpress/2009/12/06/attempting-to-unwind-the-tangled-web-of-pid-file-creation/feed/" rel="self" type="application/rss+xml" />
	<link>http://ebergen.net/wordpress/2009/12/06/attempting-to-unwind-the-tangled-web-of-pid-file-creation/</link>
	<description>You will probably want some waders, a pickaxe, and one of those hats with a light on it before you go in here.</description>
	<lastBuildDate>Fri, 13 Jan 2012 16:39:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Log Buffer #172: a Carnival of the Vanities for DBAs &#124; The Pythian Blog</title>
		<link>http://ebergen.net/wordpress/2009/12/06/attempting-to-unwind-the-tangled-web-of-pid-file-creation/comment-page-1/#comment-261689</link>
		<dc:creator>Log Buffer #172: a Carnival of the Vanities for DBAs &#124; The Pythian Blog</dc:creator>
		<pubDate>Fri, 11 Dec 2009 18:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://ebergen.net/wordpress/?p=346#comment-261689</guid>
		<description>[...] long as we&#8217;re in /var, here&#8217;s Eric Bergen attempting to unwind the tangled web of pid file creation, which he started doing having discovered a pid file creation race condition in [...]</description>
		<content:encoded><![CDATA[<p>[...] long as we&#8217;re in /var, here&#8217;s Eric Bergen attempting to unwind the tangled web of pid file creation, which he started doing having discovered a pid file creation race condition in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antony Curtis</title>
		<link>http://ebergen.net/wordpress/2009/12/06/attempting-to-unwind-the-tangled-web-of-pid-file-creation/comment-page-1/#comment-261304</link>
		<dc:creator>Antony Curtis</dc:creator>
		<pubDate>Mon, 07 Dec 2009 06:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://ebergen.net/wordpress/?p=346#comment-261304</guid>
		<description>Just FYI, __EMX__ denotes OS/2 using the EMX runtime, originally developed by Eberhard Mattes to port unix applications to the OS/2 platform.</description>
		<content:encoded><![CDATA[<p>Just FYI, __EMX__ denotes OS/2 using the EMX runtime, originally developed by Eberhard Mattes to port unix applications to the OS/2 platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bergen</title>
		<link>http://ebergen.net/wordpress/2009/12/06/attempting-to-unwind-the-tangled-web-of-pid-file-creation/comment-page-1/#comment-261292</link>
		<dc:creator>Eric Bergen</dc:creator>
		<pubDate>Mon, 07 Dec 2009 03:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://ebergen.net/wordpress/?p=346#comment-261292</guid>
		<description>It doesn&#039;t fix it. It just makes it far less likely. Innodb initialization can take minutes or even hours to finish depending on how much work it has to do. WIth my patch the pid file is created after args are parsed.

In the specific case I ran into while testing some changes to mysqld_safe the race was between me switching terminals to kill mysqld and the pid file being created. I often &quot;won&quot; that race due to the time it takes to initialize innodb. With this patch I can&#039;t win because the time before creating the pid file has been significantly reduced. 

There is also another side case which is allowing two mysqlds to start on the same directly and perform storage engine initialization. Anyone that has had this happen with innodb has seen the flurry of file locking errors innodb spits out when this happens. This patch doesn&#039;t fix that race condition either but makes it significantly less likely to happen.</description>
		<content:encoded><![CDATA[<p>It doesn&#8217;t fix it. It just makes it far less likely. Innodb initialization can take minutes or even hours to finish depending on how much work it has to do. WIth my patch the pid file is created after args are parsed.</p>
<p>In the specific case I ran into while testing some changes to mysqld_safe the race was between me switching terminals to kill mysqld and the pid file being created. I often &#8220;won&#8221; that race due to the time it takes to initialize innodb. With this patch I can&#8217;t win because the time before creating the pid file has been significantly reduced. </p>
<p>There is also another side case which is allowing two mysqlds to start on the same directly and perform storage engine initialization. Anyone that has had this happen with innodb has seen the flurry of file locking errors innodb spits out when this happens. This patch doesn&#8217;t fix that race condition either but makes it significantly less likely to happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davi Arnaut</title>
		<link>http://ebergen.net/wordpress/2009/12/06/attempting-to-unwind-the-tangled-web-of-pid-file-creation/comment-page-1/#comment-261290</link>
		<dc:creator>Davi Arnaut</dc:creator>
		<pubDate>Mon, 07 Dec 2009 03:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://ebergen.net/wordpress/?p=346#comment-261290</guid>
		<description>So, how does this fix the race that you mentioned? It seems that the patch only makes it more unlikely to happen.</description>
		<content:encoded><![CDATA[<p>So, how does this fix the race that you mentioned? It seems that the patch only makes it more unlikely to happen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

