What follows are all the write actions related to unicorn pid file when doing a hot restart. Seems like a bug to me that unicorn is deleting the pid file before writing the new file. Is there a reason for it? It seems to go against that rename that aims for an atomic replace that would always ensure the pid file is there.
Regards, Petteri 2012-11-26 00:54:12 +0200 [:delete] "unicorn_blue1.pid" 2012-11-26 00:54:12 +0200 [:create] "0.18100578716567672.15108" 2012-11-26 00:54:12 +0200 [:open] "0.18100578716567672.15108" 2012-11-26 00:54:12 +0200 [:modify] "0.18100578716567672.15108" 2012-11-26 00:54:12 +0200 [:moved_from, :move] "0.18100578716567672.15108" 2012-11-26 00:54:12 +0200 [:moved_to, :move] "unicorn_blue1.pid.oldbin" 2012-11-26 00:54:12 +0200 [:close_write, :close] "unicorn_blue1.pid.oldbin" 2012-11-26 00:54:14 +0200 [:create] "0.9762316483892712.16822" 2012-11-26 00:54:14 +0200 [:open] "0.9762316483892712.16822" 2012-11-26 00:54:14 +0200 [:modify] "0.9762316483892712.16822" 2012-11-26 00:54:14 +0200 [:moved_from, :move] "0.9762316483892712.16822" 2012-11-26 00:54:14 +0200 [:moved_to, :move] "unicorn_blue1.pid" 2012-11-26 00:54:14 +0200 [:close_write, :close] "unicorn_blue1.pid" 2012-11-26 00:54:14 +0200 _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
