OK but say you are running `merb -d -c 5 -p 4000` and then you run the
same thing again before sending INT to the first process, you will
just get a fatal message saying that merb is already running on that
port...

On Nov 19, 6:17 pm, "Yehuda Katz" <[EMAIL PROTECTED]> wrote:
> Ha :)
> Sorry about that.
>
> At the moment, what you need to do is grab the PID from merb.main.pid, start
> up a new process using whatever command you normally use to start up the
> process, and then send an INT to the original PID. The other options atm,
> using merb -K, require that you wait until the processes die before you can
> start up the new process. This option allows you to have the new processes
> primed and waiting for the old workers to die off.
>
> -- Yehuda
>
> On Wed, Nov 19, 2008 at 9:58 AM, Michael D'Auria
> <[EMAIL PROTECTED]>wrote:
>
>
>
> > I actually asked a similar question with no response.  I hope you are
> > luckier than I :)
>
> > On Wed, Nov 19, 2008 at 12:12 PM, Dermot Brennan <[EMAIL PROTECTED]
> > > wrote:
>
> >> I have a merb 1.0 application that I am deploying using capistrano.
> >> What is the best way of reloading the code after redeployment?
>
> >> merb -K all isn't working reliably for me and merb --fast-deploy
> >> doesn't reload the init.rb and gems.
>
> >> kill -HUP `cat log/merb.main.pid`
> >> restarts the work processes but I don't think it reloads the code.
>
> >> At the moment I have resorted to just killing all merb process and
> >> restarting the merb master process but that's not a graceful solution.
> >> Is there a better way?
>
> >> -Dermot
>
> --
> Yehuda Katz
> Developer | Engine Yard
> (ph) 718.877.1325
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to