Apologies for necroing a 3-year old post. However, it’s still quite relevant. For those catching up, the original question was “We can start bench, and restart bench…how can we stop it?”
First, a short demonstration of why “CTRL + C” won’t always work. In your bash shell, simply do this:
bench start $
Now, bench is running in the background.
- Yes, I know you can return this to the foreground, using fg.
- Yes, I know you can hunt for processes using ps aux | grep bench, and a dozen different variations.
- Yes, I know this issue doesn’t happen in Production.
With all that said…it’s still a pain.
Folks, we have at least 50 different bench commands. How about we add just 1 more, to automatically kill Bench/Frappe/ERPNext. No matter whether it’s running in the foreground, background, underground, or coffee ground.
I’ll give you a few days to convince me that I’m asking for crazy things. Otherwise, I’ll open an Issue in GitHub against Bench.