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.

Sign up for GitHub

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

Jump to bottom

Not possible to call kill(pid, 0) #441

Closed
mkollaro opened this issue Oct 22, 2016 · 1 comment
Closed

Not possible to call kill(pid, 0) #441

mkollaro opened this issue Oct 22, 2016 · 1 comment

Comments

@mkollaro
Copy link

According to the man page:

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.

The current signature is pub fn kill(pid: pid_t, signal: Signal), and I think it should use Option<Signal>.
@fiveop fiveop mentioned this issue Oct 24, 2016
Merged
@kamalmarhubi
Copy link
Member

Thanks for the report. This is being handled in #445, which is close to done.

homu added a commit that referenced this issue Nov 14, 2016
@homu
Auto merge of #445 - fiveop:kill_optional_signal, r=@kamalmarhubi
6b26884 
Make signal argument to kill optional

Fixes #441
@homu homu closed this as completed in #445 Nov 14, 2016
@fiveop fiveop mentioned this issue Feb 15, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kamalmarhubi @mkollaro