Alan Pinstein

Yeah I suppose that could work as well. I was just trying to keep the concern separate since I didn't know what else was going on. Thanks for reviewing! On...

@eric your idea only half worked; the pid needed to be cleared out on de-register so that it would re-bootstrap itself based on the watch/pid file. Otherwise it would continue...

I have reduced this to a smaller test case and figured out the problem... if a monitored service is restarted out-of-band (where the old proc exits and a new one...

I worked through this a bit today with a colleague and we managed to find a fix, though I have no idea if there are additional consequences to consider: https://github.com/mojombo/god/pull/142...

I should note I am using keepalive; maybe that's part of the problem is that the default keepalive handlers don't expect this.

Starting to play around with ideas for this refactor on https://github.com/apinstein/climax/tree/subcommand-refactor

Also we should probably consider finishing up the separate library that offers combined error/exception handling (like phocoa) and use that to capture errors as well as exceptions.

IIRC I have merged in all of technicalpickles stuff into master, I just don't think he ever pushed the new gem. He set it up so I can't... You should...

So, mine is the canonical, but technicalpickles forked mine and published that to RubyGems before we got in touch with each other. Madness has ensued. I worked with him months...

Ah well in that case you should probably get away with copy/paste rather than refactoring. If you end up with a nice library then maybe we could refactor capistrano-gitflow to...