# Monitoring daemon in monitrc

**URL:** <https://www.ruby-forum.com/t/monitoring-daemon-in-monitrc/166558>\
**Category:** Deployment\
**Created:** [April 27, 2009, 12:47pm UTC](https://www.ruby-forum.com/t/monitoring-daemon-in-monitrc/166558 "2009-04-27T12:47:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chunkyslink](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f0a364/32.png) [@chunkyslink](https://www.ruby-forum.com/u/chunkyslink)\
**Post date:** [April 27, 2009, 12:47pm UTC](https://www.ruby-forum.com/t/monitoring-daemon-in-monitrc/166558/1 "2009-04-27T12:47:59Z")

</div>

Would anyone know which is the correct start / stop monitrc  
configuration for a daemon running on the ‘daemons’ gem (as seen in the  
Custom Daemons Railscast)?

check process reminder\_mailer  
with pidfile /var/www/notipal/current/log/mailer.rb\_monitor.pid

# Option 1

start program = “/var/www/notipal/shared/scripts/mailer\_worker.sh  
start”  
stop program = “/var/www/notipal/shared/scripts/mailer\_worker.sh stop”

# Option 2

#start program = “/var/www/notipal/current/lib/daemons/mailer\_ctl  
start”  
#stop program = “/var/www/notipal/current/lib/daemons/mailer\_ctl stop”  
if totalmem is greater than 120 MB for 2 cycles then restart

[http://pastie.org/private/w5w6wzypok3xnmuzcxdsw](http://pastie.org/private/w5w6wzypok3xnmuzcxdsw)

The Railscast suggests it’s the mailer\_ctl, but the last dev on this app  
used mailer\_worker.sh…

Thanks