-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Unable to force kill a sleep #473
Comments
You've now reached the point where the abstractions break down and the implementation details start to leak out. This has been discussed previously in issue #375. It sometimes happens that If you run Running it as a command substitution is more complex. If I add a call to
The pid reported by I'd also modified the script so it passed the negative of the pid to
On Linux using a negative pid signals a process group. In busybox-w32 it approximates this by signalling the given pid and all its children. In the example above the effect of this was to kill process 2588 and its child, 2876, the Whether this would work for you depends on what you actually want to achieve in your application. |
The The example with sleep and a negative pid seems to work on busybox-w32 but on bash online it say: Do you know why it say this? |
I don't know. My guess would be that the background process isn't a process group leader. (Though I must confess my knowledge of such things is minimal.) |
Thanks for the reply. PS: If there is someone that have an idea feel free to post even if it is closed. |
Sample code:
I expected to see "End" after 1 second, but it doesn't work.
The text was updated successfully, but these errors were encountered: