Better way to deal with unexpected termination about overmind HOT 3 CLOSED

I hope, #86 fixes this. I honestly don't know a better way to handle this.

from overmind.

I run into this all the time Here's what it looks like:

% overmind start
system | Tmux socket name: overmind-foobar-md7CP2HbTfJJglZ105B-cO
system | Tmux session ID: foobar
system | Listening at ./.overmind.sock
overmind: it looks like Overmind is already running. If it's not, remove ./.overmind.sock and try again

I figure it's already running in one of my tabs, so I do:

% overmind restart
overmind: dial unix ./.overmind.sock: connect: connection refused

Oh, looks like it's not running after all. Must be a stale .sock file.

% rm .overmind.sock
% overmind start

It gets a bit repetitive doing this over and over again.

Is there a way to have overmind start check if it's indeed still active and it not delete any stale sock files?

from overmind.

This fixed it for me in v2.2.0. Thanks!

from overmind.