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

[krisleech]

trafficstars

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]

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.