On Tue, Dec 10, 2013 at 10:44 PM, Petteri Räty <[email protected]> wrote:
> At least for pid based monitoring tools it is (I do agree with others > that you should also be monitoring http though). For example monit > requires that you give it a pid file. Why is it wrong for them to point > to the same pid? Monit doesn't require a pid, never has: http://mmonit.com/monit/documentation/monit.html#connection_testing To answer your question, though, the reason the pid files must contain different PIDs is that the two processes (previous and current-generation masters) have different PIDs. And some of us do care that they differ :) --Michael _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
