On Thu, 12 Apr 2007 13:35:06 -0700 "Michael A. Schoen" <[EMAIL PROTECTED]> wrote:
> Bradley Taylor wrote: > > mongrel_rails stop accepts a --wait argument. If I add that to > > mongrel_cluster, will it solve these issues? > > Not for me I don't think. Again, I may be misreading it, but that --wait > argument just looks like it literally waits, then does a hard kill. I > would have expected that option to send a TERM, then wait up to @wait > seconds for it to go away, and do a KILL if it was still there. If that > were the implementation it sounds like it would work for most folks. Michael, Try running: killall -USR2 mongrel_rails and see if that works the way you expect it to work. That's the signal to tell Mongrel to do a stop/wait/start process (the real restart). Next version of mongrel_cluster will just do this. -- 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/ _______________________________________________ Mongrel-users mailing list [EMAIL PROTECTED] http://rubyforge.org/mailman/listinfo/mongrel-users
