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: > > 1. the new master does die, and the old master does work again > > 2. the "old" master keeps running with a process name of "master (old)" > > 3. the "old" master keeps running with a pid file named unicorn.pid.oldbin > > Because the file is now named unicorn.pid.oldbin a later attempt to > deploy using scripts is made rather difficult as they assume a pid file > named unicorn.pid. > > How could I get unicorn to rename the pid file back to unicorn.pid ? I > see some code in method +reap_all_workers+ that suggests it would rename > the pid file back to its original, but for some reason it doesn't for > me. Am I missing a step?
Hi Lawrence, Are you using a config file to specify pid or --pid from the command-line? The config file should be more reliable. I'll take a deeper look at it in a bit. -- 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
