Seems like it.
> What was the reason for this change; because it wasn't portable (unix only)?
> Has it something to do with moving over to Rack?
They're not particularly portable, nor are they particularly useful.
Every project I've worked on uses some other method of process
spawning and monitoring. Monit, God, Runit, mongrel_cluster, etc.
Shipping with a mostly-broken set of scripts doesn't seem like
something we should do.
2.3 is probably a while off, so hopefully the cobwebs get blown out
and no one even notices :).
> Default Capistrano recipe
> kinda relies on these and I use them in most of my projects that aren't on
> Passenger.
I think we'll send jamis some patches to change the default capistrano
recipes, or remove them entirely, or something.
> # Mislav
>
>
>
> >
>
--
Cheers
Koz
> They're not particularly portable, nor are they particularly useful.
> Every project I've worked on uses some other method of process
> spawning and monitoring. Monit, God, Runit, mongrel_cluster, etc.
> Shipping with a mostly-broken set of scripts doesn't seem like
> something we should do.
I could say the contrary, on every project with a solid Mongrel or FCGI
based setup the spawner script was used. It requires no extra
configuration unlike monit/god/runit. It also cares for safely exiting a
process *after* the current request was processed unlike the defaults for
monit/god/runit etc.
The same can be said about reaper, it *always* works as long as you invoke
it with a /full/path/to/current/process/reaper.
In what way did you find them to be broken?
--
Company - http://primalgrasp.com
Thoughts - http://deezsombor.com
I could say the contrary, on every project with a solid Mongrel or FCGI
based setup the spawner script was used. It requires no extra
configuration unlike monit/god/runit. It also cares for safely exiting a
process *after* the current request was processed unlike the defaults for
monit/god/runit etc.
In what way did you find them to be broken?
Spawner *is a monitoring superb daemon*, as long as you start Mongrels as
described in:
http://capify.org/getting-started/from-the-beginning
instead of relying on mongrel_rails.