[Mongrel] Why not ignore stale PID files?

Scott Windsor swindsor at gmail.com
Tue Jun 10 21:24:58 EDT 2008


Has anyone considering turning the mongrel_cluster into a process manager
daemon?

I know that generally many people rely on other applications (such as monit)
to ensure that mongrels are up and running, but it seems that integrated
process management out of the box would be a large win.  The mongrel_cluster
could remain running (rather than exiting) and keep track of the running
mongrels (potentially restarting them if they die or zombie).  At that
point, pid files become uneeded for tracking running mongrels.  The only
exception would be if the mongrel cluster itself dies - at this point it
would orphan the child processes and it would up to the cluster to kill off
(or resume ownership) of any orphaned processes.

thoughts?

- scott

On Tue, Jun 10, 2008 at 4:50 PM, Jos Backus <jos at catnook.com> wrote:

> On Wed, Jun 11, 2008 at 01:25:41AM +0200, Hongli Lai wrote:
> > PID files suck.
>
> Agreed. Just use daemontools or runit or some other process manager - no
> pidfiles or complicated locking code needed.
>
> --
> Jos Backus
> jos at catnook.com
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/mongrel-users/attachments/20080610/9060e1fc/attachment.html>


More information about the Mongrel-users mailing list