# Monitor ferret Drb with launchd on OS X

**URL:** <https://www.ruby-forum.com/t/monitor-ferret-drb-with-launchd-on-os-x/144669>\
**Category:** Ferret\
**Created:** [August 1, 2008, 1:38am UTC](https://www.ruby-forum.com/t/monitor-ferret-drb-with-launchd-on-os-x/144669 "2008-08-01T01:38:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![E\_Durante](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/d78d45/32.png) [@E\_Durante](https://www.ruby-forum.com/u/E_Durante)\
**Post date:** [August 1, 2008, 1:38am UTC](https://www.ruby-forum.com/t/monitor-ferret-drb-with-launchd-on-os-x/144669/1 "2008-08-01T01:38:31Z")

</div>

Has anyone tried monitoring the ferret Drb server with launchd (OS X)?  
Does anyone know if there is any limitation that would prevent ferret  
from being monitored by launchd? I have tried many different plists  
and none work. One starts too many ferret servers and one cannot  
start any server. If anyone has experience with this, any information  
would be most appreciated.

Thanks.

---

<div class="post-metadata">

**Author:** ![E\_Durante](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/d78d45/32.png) [@E\_Durante](https://www.ruby-forum.com/u/E_Durante)\
**Post date:** [August 2, 2008, 11:37pm UTC](https://www.ruby-forum.com/t/monitor-ferret-drb-with-launchd-on-os-x/144669/2 "2008-08-02T23:37:23Z")

</div>

I figured it out. I am using AAF gem v. 0.4.3 which has a new  
ferret\_server wrapper which does not have a non-daemonizing option.  
This patch fixes the problem:

[Patch] Allow ferret\_server to run in blocking (non-daemon) mode  
[http://projects.jkraemer.net/acts\_as\_ferret/ticket/184](http://projects.jkraemer.net/acts_as_ferret/ticket/184)

If you are getting a lot of “Throttling respawn: Will start in x  
seconds” messages in your logs, and notice that you have way more ruby  
processes running than you had ever planned, check out this patch.