Process is not killed #42

fkill :3000 -f

it would be nice if fkill would reflect the fact that it did not kill the process in the output. Also IMHO the default to forcibly kill it would make more sense to me. I mean if someone is installing fkill it is because they want to kill processes, not just ask them nicely to terminate.

In the interactive interface, we detect if the process was killed or not and ask the user if they want to force kill. When using the non-interactive interface, like here, we could try to force kill if normal killing didn't work.

@issuehunt has funded $40.00 to this issue. See it on IssueHunt

When using the non-interactive interface, like here, we could try to force kill if normal killing didn't work.

@sindresorhus Should we introduce a new flag for this behavior? Something like safe-kill? We could also just notify the user that a process is going to get killed forcibly when normal killing didn't work.

I think we should try killing normally first and if that fails, we should force kill.

@sindresorhus that makes the assumption that fkill knows how long the process takes to cleanly shutdown. Perhaps if it prompts the user so they know they are about the rip the life from the process without giving it time to clean up.

If anyone wants to work on this, see the initial attempt and feedback here: https://github.com/sindresorhus/fkill-cli/pull/70

This is blocked by https://github.com/sindresorhus/fkill/issues/44

Abandoned attempt: https://github.com/sindresorhus/fkill-cli/pull/76

@sindresorhus has rewarded $36.00 to @stroncium. See it on IssueHunt

• :moneybag: Total deposit: $40.00
• :tada: Repository reward(0%): $0.00
• :wrench: Service fee(10%): $4.00