Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@dmur1
Copy link

@dmur1 dmur1 commented Apr 17, 2025

previously code dealing with sigFatal assumed that the value is either 0 or a value representing a single type of signal

previously code dealing with sigFatal assumed that the value is either 0 or a value representing a single type of signal
@google-cla
Copy link

google-cla bot commented Apr 17, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

} else {
removeProc(nsjconf, pid);
}
kill(pid, signal);
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this is a mistake.. if kill returns 0 we should call removeProc otherwise we'll sit here forever

@dmur1 dmur1 marked this pull request as draft April 17, 2025 19:39
@dmur1
Copy link
Author

dmur1 commented Apr 17, 2025

@robertswiecki i think this does need a real good looking at before its accepted - consider that its really not tested and just suggestion about how the underlying issue could be fixed

i think i haven't really properly understood the function of killAndReapAll - the issue i tried to fix was that we want to be able to forward multiple signals to a process without the first signal resulting in a call to reapProc

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

Successfully merging this pull request may close these issues.

1 participant