Lawrence Pit <[email protected]> wrote: > Hi, > > I followed the procedure to replace a running unicorn. Works fine, > except for one thing: after I decide to back out, ie I send a HUP to the > old master followed by a QUIT to the new master, then:
Ah, ok. I can reproduce it. The problem is the HUP by the old master tries to reset the pid file to the non-"oldbin" version which the new master is still holding on to. You could QUIT the new master first and then HUP, but this is _far_ from ideal because it leaves you with a window without running workers (and also it contradicts our documentation). It's also difficult to avoid race conditions this way. I'm looking for a better way to go about this, pid files are nasty :x -- Eric Wong _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
