<?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: new ebuild for Nginx</title>
	<atom:link href="http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/feed/" rel="self" type="application/rss+xml" />
	<link>http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/</link>
	<description>de arte technologiæ</description>
	<lastBuildDate>Fri, 03 Sep 2010 16:12:50 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mark</title>
		<link>http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/comment-page-1/#comment-8402</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Thu, 25 Feb 2010 11:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://mark.ossdl.de/?p=529#comment-8402</guid>
		<description>Juan, I&#039;ve read the FHS, and watched its creation process since the beginning. When having seen many systems and its quirks, you will quickly realize there is no way around standardization. You got a valid point, so it is good we discuss about it.

By introducing the artificial requirement for a subdirectory, indeed, there is no way around using &lt;cite&gt;/var/tmp&lt;/cite&gt;. Just keep in mind it works perfectly (and faster) without that, and we still can create the empty directories by start scripts.

Till Nginx 0.8.34 is released you can fork the overlay. Every &lt;code&gt;git fetch; git merge&lt;/code&gt; will preserve your adaption. And yet still you can tweak your configuration files. Nothing is written in stone. ^_~</description>
		<content:encoded><![CDATA[<p>Juan, I&#8217;ve read the FHS, and watched its creation process since the beginning. When having seen many systems and its quirks, you will quickly realize there is no way around standardization. You got a valid point, so it is good we discuss about it.</p>
<p>By introducing the artificial requirement for a subdirectory, indeed, there is no way around using <cite>/var/tmp</cite>. Just keep in mind it works perfectly (and faster) without that, and we still can create the empty directories by start scripts.</p>
<p>Till Nginx 0.8.34 is released you can fork the overlay. Every <code>git fetch; git merge</code> will preserve your adaption. And yet still you can tweak your configuration files. Nothing is written in stone. ^_~</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juan Giordana</title>
		<link>http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/comment-page-1/#comment-8399</link>
		<dc:creator>Juan Giordana</dc:creator>
		<pubDate>Thu, 25 Feb 2010 03:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://mark.ossdl.de/?p=529#comment-8399</guid>
		<description>Hey Mark,

Sorry for being a pain :P on the subject but:

&quot;The /var/tmp directory is made available for &lt;strong&gt;programs&lt;/strong&gt; that &lt;strong&gt;require&lt;/strong&gt; temporary files or &lt;strong&gt;directories&lt;/strong&gt; that are preserved between system reboots.&quot;

Nginx &lt;strong&gt;requires&lt;/strong&gt; those directories to start, not the files inside them.

Have a look at the diferences on the FHS, /var/tmp is the right place. 

http://www.pathname.com/fhs/pub/fhs-2.3.html#TMPTEMPORARYFILES

http://www.pathname.com/fhs/pub/fhs-2.3.html#VARTMPTEMPORARYFILESPRESERVEDBETWEE

Regards</description>
		<content:encoded><![CDATA[<p>Hey Mark,</p>
<p>Sorry for being a pain <img src='http://cdn.ww.ossdl.de/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' />  on the subject but:</p>
<p>&#8220;The /var/tmp directory is made available for <strong>programs</strong> that <strong>require</strong> temporary files or <strong>directories</strong> that are preserved between system reboots.&#8221;</p>
<p>Nginx <strong>requires</strong> those directories to start, not the files inside them.</p>
<p>Have a look at the diferences on the FHS, /var/tmp is the right place. </p>
<p><a href="http://www.pathname.com/fhs/pub/fhs-2.3.html#TMPTEMPORARYFILES" rel="nofollow">http://www.pathname.com/fhs/pub/fhs-2.3.html#TMPTEMPORARYFILES</a></p>
<p><a href="http://www.pathname.com/fhs/pub/fhs-2.3.html#VARTMPTEMPORARYFILESPRESERVEDBETWEE" rel="nofollow">http://www.pathname.com/fhs/pub/fhs-2.3.html#VARTMPTEMPORARYFILESPRESERVEDBETWEE</a></p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/comment-page-1/#comment-8389</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Tue, 23 Feb 2010 18:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://mark.ossdl.de/?p=529#comment-8389</guid>
		<description>Even if &lt;cite&gt;/tmp&lt;/cite&gt; is &#039;wiped&#039;, the directory itself is preserved. I have tested it several times, and Nginx &lt;strike&gt;works&lt;/strike&gt; starts fine.

But given the demand, I will include a check in future Ebuilds so you can set &lt;cite&gt;/var/tmp&lt;/cite&gt; as temporaries&#039; directory. (Which will be, Juan, not FHS compliant. But there is no harm, either.)</description>
		<content:encoded><![CDATA[<p>Even if <cite>/tmp</cite> is &#8216;wiped&#8217;, the directory itself is preserved. I have tested it several times, and Nginx <strike>works</strike> starts fine.</p>
<p>But given the demand, I will include a check in future Ebuilds so you can set <cite>/var/tmp</cite> as temporaries&#8217; directory. (Which will be, Juan, not FHS compliant. But there is no harm, either.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juan Giordana</title>
		<link>http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/comment-page-1/#comment-8388</link>
		<dc:creator>Juan Giordana</dc:creator>
		<pubDate>Tue, 23 Feb 2010 18:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://mark.ossdl.de/?p=529#comment-8388</guid>
		<description>Hello Mark,

Having the temporary paths set to /tmp will make the nginx startup script to fail if the system is rebooted since that directory could be wiped via /etc/conf.d/bootmisc or, as you mentioned, being on tmpfs.

You should either create those /tmp/nginx/* directories from within the startup script or keep using /var/tmp/nginx/* which is FHS compliant (&quot;/var/tmp : Temporary files preserved between system reboots&quot;) for this particular case.</description>
		<content:encoded><![CDATA[<p>Hello Mark,</p>
<p>Having the temporary paths set to /tmp will make the nginx startup script to fail if the system is rebooted since that directory could be wiped via /etc/conf.d/bootmisc or, as you mentioned, being on tmpfs.</p>
<p>You should either create those /tmp/nginx/* directories from within the startup script or keep using /var/tmp/nginx/* which is FHS compliant (&#8220;/var/tmp : Temporary files preserved between system reboots&#8221;) for this particular case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dm</title>
		<link>http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/comment-page-1/#comment-8170</link>
		<dc:creator>Dm</dc:creator>
		<pubDate>Fri, 29 Jan 2010 23:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://mark.ossdl.de/?p=529#comment-8170</guid>
		<description>Maybe, but this folders must not be the same by default when running nginx at first time.

client-body-temp-path &amp; proxy-temp-path are new options in nginx and without it default values nginx old configs are broken</description>
		<content:encoded><![CDATA[<p>Maybe, but this folders must not be the same by default when running nginx at first time.</p>
<p>client-body-temp-path &amp; proxy-temp-path are new options in nginx and without it default values nginx old configs are broken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/comment-page-1/#comment-8168</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Fri, 29 Jan 2010 16:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://mark.ossdl.de/?p=529#comment-8168</guid>
		<description>Dm, how would this be a fix?

Indeed, on most servers I&#039;ve seen &lt;cite&gt;/tmp&lt;/cite&gt; being on (transient) &lt;cite&gt;tmpfs&lt;/cite&gt; and &lt;cite&gt;/var/tmp&lt;/cite&gt; being a larger, but persistent temporaries&#039; folder on HDD which is preserved between system reboots. - What conforms to &lt;a href=&quot;http://www.pathname.com/fhs/pub/fhs-2.3.html&quot; rel=&quot;nofollow&quot;&gt;FHS 2.3&lt;/a&gt;.

Finally, Nginx does not create subfolders on its own, creates temporary files in a safe manner and does not assume they exist between two program invocations. 

Therefore &lt;cite&gt;/tmp&lt;/cite&gt; (or anything beneath it) is the only correct place.</description>
		<content:encoded><![CDATA[<p>Dm, how would this be a fix?</p>
<p>Indeed, on most servers I&#8217;ve seen <cite>/tmp</cite> being on (transient) <cite>tmpfs</cite> and <cite>/var/tmp</cite> being a larger, but persistent temporaries&#8217; folder on HDD which is preserved between system reboots. &#8211; What conforms to <a href="http://www.pathname.com/fhs/pub/fhs-2.3.html" rel="nofollow">FHS 2.3</a>.</p>
<p>Finally, Nginx does not create subfolders on its own, creates temporary files in a safe manner and does not assume they exist between two program invocations. </p>
<p>Therefore <cite>/tmp</cite> (or anything beneath it) is the only correct place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dm</title>
		<link>http://mark.ossdl.de/2010/01/new-ebuild-for-nginx/comment-page-1/#comment-8167</link>
		<dc:creator>Dm</dc:creator>
		<pubDate>Fri, 29 Jan 2010 15:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://mark.ossdl.de/?p=529#comment-8167</guid>
		<description>Please fix in nginx.eclass [199-201] as in original www-servers/nginx

&lt;pre class=&quot;brush: text&quot;&gt;--http-client-body-temp-path=/var/tmp/${PN}/client \
--http-proxy-temp-path=/var/tmp/${PN}/proxy \
--http-fastcgi-temp-path=/var/tmp/${PN}/fastcgi \&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>Please fix in nginx.eclass [199-201] as in original www-servers/nginx</p>
<pre class="brush: text">--http-client-body-temp-path=/var/tmp/${PN}/client \
--http-proxy-temp-path=/var/tmp/${PN}/proxy \
--http-fastcgi-temp-path=/var/tmp/${PN}/fastcgi \</pre>
]]></content:encoded>
	</item>
</channel>
</rss>
