Re: writing pid file earlier

Lets say you alter the code.

What happens if the PID file is written, but Mongrel dies kicking off
the Rails app (because you have a problem with your Rails code)? Won’t
god* then think that your process is running when it isn’t? Isn’t this
false positiver worse than a couple false negatives?

Seems to me that if you can’t tell god* to wait long enough for your
process to start, maybe god* isn’t the answer…

==
Will G.

John Joseph B. wrote …

On Jan 24, 2008 11:43 AM, Will G. [email protected] wrote:

Lets say you alter the code.

What happens if the PID file is written, but Mongrel dies kicking off the Rails app (because you have a problem with your Rails code)? Won’t god* then think that your process is running when it isn’t? Isn’t this false positiver worse than a couple false negatives?

Well, IMHO, mongrel should write the pid file early, and clean the pid
file up when it dies, for whatever reason short of something
untrappable like a segfault.

Kirk H.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs