-
Notifications
You must be signed in to change notification settings - Fork 59
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
option to send SIGKILL? #136
Comments
We can add a
@iffyuva Any ideas? |
Something like that would be great for my use case! |
I think this should be added to the CLI, i.e. |
It already is implemented and has been there since very beginning:
Which will remove sidekiq with signal 9. However when you will Invoker and it quits, all processes are attempted to be killed via TERM signal. |
@gnufied I was thinking, instead of just 9, invoker should act as a shim for process commands, e.g it would be useful to send |
I have a process that doesn't always respond to the SIGTERM signal and remains running; however invoker shuts down and loses track of this PID leaving an orphaned process around; I've used foreman/forego in the past and it tries to send a SIGTERM, waits a while and then issues SIGKILL on any remaining processes before stopping which cleans up everything correctly. Is it possible to do the same with invoker?
The text was updated successfully, but these errors were encountered: