hi all, wouldn't this be really useful for updating production servers as well? instead of taking down all mongrels at once, you could restart one after another. so you have zero downtime, and depeding on how smart your script is even cancel restart of mongrel n+1 if mongrel n hasn't come up successfully.
cheers, phillip --- Am 18.12.2006 um 10:53 schrieb Zed A. Shaw: > On Mon, 18 Dec 2006 09:52:45 +0100 > Kaspar Schiess <[EMAIL PROTECTED]> wrote: > >> Hi list, >> >> I have tried to reach Bradley (author of mongrel_cluster) by mail, >> but >> have not gotten a response. So I'll try trough this channel: >> > > Send it to me offlist and I'll take a look at it. Thanks. > > -- > Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu > http://www.zedshaw.com/ > http://www.awprofessional.com/title/0321483502 -- The Mongrel Book > http://mongrel.rubyforge.org/ > http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help. > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > > ------------- Phillip Oertel Manager Engineering [EMAIL PROTECTED] Open Business Club AG, XING Gaensemarkt 43, 20354 Hamburg, Germany Tel +49 40 41 91 31-754, Fax +49 40 41 91 31-11 Please join my network on XING: http://www.xing.com/profile/Phillip_Oertel This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden and may be unlawful. _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
