Skip to content
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

kill does not allow 0 as a signal #504

Closed
gcp opened this issue Feb 1, 2017 · 1 comment
Closed

kill does not allow 0 as a signal #504

gcp opened this issue Feb 1, 2017 · 1 comment

Comments

@gcp
Copy link

gcp commented Feb 1, 2017

   "If sig is 0, then no signal is sent, but error checking is still performed; this can be used to  check
   for the existence of a process ID or process group ID."

signal.rs seems to explicitly disallow the signal value to be 0, i.e.:

    pub fn from_c_int(signum: libc::c_int) -> Result<Signal> {
        match 0 < signum && signum < NSIG {
@fiveop
Copy link
Contributor

fiveop commented Feb 15, 2017

We have not released it yet, but in the next version you can pass None to kill in order to pass no signal. (see #441 and #445).

@fiveop fiveop closed this as completed Feb 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants