We use a limit of around 110 - 130 It really sucks as a solution though...
On Oct 31, 1:08 pm, John Nunemaker <[EMAIL PROTECTED]> wrote: > Yeah, or you can disable the monitoring of mongrel before a longer > change. I believe because all the mongrel checks have the group > 'mongrel' I can start/stop monitoring on them all at once without > turning monit on and off. > > On Oct 30, 2007, at 3:28 PM, Rafael G. wrote: > > > jnunemaker escribió: > > >> if failed port 8000 protocol http > >> with timeout 10 seconds > >> then restart > >> group mongrel > > > [OT] This configuration I thought it isn't very correct. Imagine if > > you > > disable your web application(for example with: cap deploy:web:disable) > > and then you make changes while monit is trying to restart mongrel it > > can be a bit annoying. Maybe will be put an "and not exists > > public/system/maintenance.html" (pseudocode not real code) ;-) > > > Regards > > > begin:vcard > > fn;quoted-printable:Rafael Garc=C3=ADa Ortega > > n;quoted-printable:Garc=C3=ADa Ortega;Rafael > > org:ASPgems S.L. > > email;internet:[EMAIL PROTECTED] > > tel;work:692686533 > > x-mozilla-html:FALSE > > url:http://www.aspgems.com > > version:2.1 > > end:vcard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
