-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Support different signals than SIGKILL #8
Comments
I can pick this up. @jkfran lmk if you have any issues/ideas on this. |
@NachiketNamjoshi, Thank you so much! My only suggestion is to keep using clap to parse this new argument. Apart from that, you are welcome to be creative 😄 |
@jkfran |
I think Sigterm and Sigkill are enough for killport. Let's see if we get requests about supporting the other signals. Feel free to contribute to any of the other issues. |
Adds support to send all signals available in `nix::sys::signal::Signal` ✅ Closes: jkfran#8 Signed-off-by: NachiketNamjoshi <nachiketnamjoshi@gmail.com>
Adds support to send all signals available in `nix::sys::signal::Signal` ✅ Closes: jkfran#8 Signed-off-by: NachiketNamjoshi <nachiketnamjoshi@gmail.com>
The
kill
command supports the command-line option to specify the signal sent to the killed processes.https://www.man7.org/linux/man-pages/man1/kill.1.html, the option
--signal
.Sending other signals than SIGKILL can be useful to reload the process listening on a certain port (like nginx), or gracefully shutdown a service, or invoke other user-defined functionality.
Relevant code:
killport/src/linux.rs
Line 176 in 3a43d03
The text was updated successfully, but these errors were encountered: