.ovemind.sock is not deleted when using `-D` - Githubissues

DarthSim / overmind

Process manager for Procfile-based applications and tmux

MIT License

2.82k stars 79 forks source link

.ovemind.sock is not deleted when using `-D` #118

Open krisleech opened 2 years ago

krisleech commented 2 years ago

Really enjoying using this tool, thanks 👍

I'm not sure if this is intended behaviour or not:

overmind start -D
.overmind.sock is created
turn off computer at end of day, turn on next day
overmind start -D

overmind: it looks like Overmind is already running. If it's not, remove ./.overmind.sock and try again

Should I manually do overmind quit or should overmind handle deleting of the sock file?

Note that the .overmind.sock is deleted if I don't use the -D option when I send a term signal.

DarthSim commented 2 years ago

Hey @krisleech! Overmind catches SIGTERM for graceful shutdown and should delete .overmind.sock when receiving SIGTERM even when daemonized. However, it waits for all processes to stop. Maybe your system kills it before this.