Bradley Taylor wrote: > Thanks Carl. I'll patch this in and push the release. Last call!
Just a question: why does a cluster restart do a stop and a start, rather than an actual restart on each Mongrel? A restart is "nicer", and handles much better cases in which a Mongrel can't (or shouldn't) stop immediately. The current stop/start approach means that the start often fails, because the stop hasn't actually shutdown the Mongrel yet. Would it be possible to make doing an actual restart an option? Or another command that does a true restart? _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
