Hi Yehuda, I think I'm missing something. If I try to start a new cluster when an old cluster is running I always get an error:
FATAL: Merb is already running on port 8701. How can I bring up the new processes so that they will wait until the port becomes available? Steve On Thu, Nov 20, 2008 at 9:03 PM, Yehuda Katz <[EMAIL PROTECTED]> wrote: > Additionally, when you start up a merb that cannot bind to a port, it does > *not* immediately crash. Instead, it waits for the ports to become > available, and binds as soon as they do. This allows you to start up a new > merb, wait for it to come up, then gracefully kill the old process. As ports > die in the old deployment, they will immediately come online in the new > cluster. > However, this cannot work if the old and new deployment are in the same > directory, because as soon as you bring up the new cluster, it overwrites > the old pid files. For restarting in this scenario (at the moment), you need > to get the main pid first, store it off, then bring up the new process, and > send an INT to the stored pid. This is easy enough with a Ruby script or > bash script, but we will be adding explicit support for this via merb > --restart in the framework itself at some point in the future. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
