<?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: Starting Mongrel or Memcached with Launchd</title>
	<atom:link href="http://michael.biven.org/2006/12/22/starting-mongrel-or-memcached-with-launchd/feed/" rel="self" type="application/rss+xml" />
	<link>http://michael.biven.org/2006/12/22/starting-mongrel-or-memcached-with-launchd/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 01:27:40 +0000</pubDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: pedz</title>
		<link>http://michael.biven.org/2006/12/22/starting-mongrel-or-memcached-with-launchd/comment-page-1/#comment-26</link>
		<dc:creator>pedz</dc:creator>
		<pubDate>Sun, 02 Dec 2007 00:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://michael.biven.org/?p=250#comment-26</guid>
		<description>First, Thank you very much.  This will help me a lot.

I played with mongrel_rails start ... from the command line.  -P and -l do not do anything if you are not going in to daemon mode.  (I'm using 1.0.1).

I'm scared to start multiple mongrels from the same plist.  I don't understand how launchd is going to decide to do two fork/execs.  So, I'm going to have a plist file for each mongrel instance.

I think I'm going to use the chdir command of the launchd.plist to get me to the rails base.  And I also think I'm going to use stdout and stderr options in the plist for the log files.</description>
		<content:encoded><![CDATA[<p>First, Thank you very much.  This will help me a lot.</p>
<p>I played with mongrel_rails start &#8230; from the command line.  -P and -l do not do anything if you are not going in to daemon mode.  (I&#8217;m using 1.0.1).</p>
<p>I&#8217;m scared to start multiple mongrels from the same plist.  I don&#8217;t understand how launchd is going to decide to do two fork/execs.  So, I&#8217;m going to have a plist file for each mongrel instance.</p>
<p>I think I&#8217;m going to use the chdir command of the launchd.plist to get me to the rails base.  And I also think I&#8217;m going to use stdout and stderr options in the plist for the log files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristofer</title>
		<link>http://michael.biven.org/2006/12/22/starting-mongrel-or-memcached-with-launchd/comment-page-1/#comment-27</link>
		<dc:creator>Kristofer</dc:creator>
		<pubDate>Tue, 27 Nov 2007 21:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://michael.biven.org/?p=250#comment-27</guid>
		<description>Thanks for the .plists. That's very helpful as a starting point. I've run into the same conceptual barrier time and time again when moving old-time daemons over to launchd. I keep forgetting that you can't start them up into daemon mode, or *even* background them.

one small niggling point: Your labels aren't standard. For example
Label
local.server.memcached

should be:
Label
com.danga.memcached</description>
		<content:encoded><![CDATA[<p>Thanks for the .plists. That&#8217;s very helpful as a starting point. I&#8217;ve run into the same conceptual barrier time and time again when moving old-time daemons over to launchd. I keep forgetting that you can&#8217;t start them up into daemon mode, or *even* background them.</p>
<p>one small niggling point: Your labels aren&#8217;t standard. For example<br />
Label<br />
local.server.memcached</p>
<p>should be:<br />
Label<br />
com.danga.memcached</p>
]]></content:encoded>
	</item>
</channel>
</rss>
