-
Notifications
You must be signed in to change notification settings - Fork 1
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 doesn't work on Ubuntu #1
Comments
That's really weird... especially since BackgroundProcess is specifically using 'exec' to execute the command... I don't know how much more 'exec-y' you can get. I've tried it on an ubuntu karmic machine, and it appears to work fine:
|
which ruby version are you using? Is it the same between OS X and your Ubuntu machine? |
We're using ruby 1.8.7 (patchlevel 174) on both. We'll see if we can reproduce it with a simpler script and upload it (at the moment we're using BackgroundProcess from within a Cucumber script, but I don't think that this is causing the issue). |
are you using output redirectors?
|
No, but we're explicitly running ruby (maybe with relative paths), which might?
When you |
When it uses the "sh -c ... " version. Does kill work for you? |
Just tried running this on OS X. It actually causes an orphan process to be left behind too.
|
I don't believe it would. I'm curious to see if that's what's reproducing it. Can you record a screencast with jing or something and share it to demonstrate the problem? Or terminal output? |
When we issue a @process.kill on ubuntu it doesn't kill it (even if we use INT). Digging in a little it looks like @process.id is the wrong pid, hence kill doesn't work.
On Ubuntu when the process is run, it runs "sh -c [my command]", which then spawns the actual command. This appears to be different from OS X where the command is executed directly (as the ruby doc implies would happen).
I assume(?) that it's the extra "sh -c" process that's causing the pid to be incorrect, since it's pointing at the "sh -c" process rather than the real command process.
We're stuck. Any help appreciated, and happy to work on it with you.
Aish
PS. The same script is working fine on OS X.
The text was updated successfully, but these errors were encountered: