New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No way to specify signal to send #31
Comments
Why do you need it? |
Sometimes programs intercept SIGTERM and don't really die, so you need to send SIGKILL (i.e. |
SIGHUP is typically used to make a daemon reload its settings (e.g. prometheus/prometheus#1572) |
This might be out of scope of fkill but I'd suggest it works like this:
|
If you're using |
This CLI is for killing processes. Sending different signals is out of scope. We already support the most common use-case by killing normally or with |
Is there a way to specify the signal to send to the process?
I understand that fkill is multi-platform but at least in Unix environment people regularly use both TERM and KILL, and possibly others like HUP
The text was updated successfully, but these errors were encountered: