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

When cancelling a run, engine processes survive #71

Open
akerbos opened this issue Nov 19, 2015 · 2 comments
Open

When cancelling a run, engine processes survive #71

akerbos opened this issue Nov 19, 2015 · 2 comments
Labels
Milestone

Comments

@akerbos
Copy link
Collaborator

akerbos commented Nov 19, 2015

When we cancel a run with CTRL+C, engine processes that were started are not (always) killed. They even survive termination of the original ltx2any process!

Investigate and resolve.

@akerbos akerbos added the bug label Nov 19, 2015
@akerbos akerbos added this to the Release 1.0 milestone Nov 19, 2015
@akerbos akerbos self-assigned this Nov 19, 2015
@akerbos
Copy link
Collaborator Author

akerbos commented Jun 17, 2016

Possible solution: store PIDs of all running child processes and skill them explicitly.

http://stackoverflow.com/questions/32965251/how-can-i-kill-process-which-has-spawned-a-child-using-system

Getting the PID is easy: f = IO::popen(...); f.pid
Killing as well: Process.kill("TERM", pid)

@akerbos
Copy link
Collaborator Author

akerbos commented Jun 17, 2016

Other possibilty: set up a signal handler.

http://stackoverflow.com/a/14636093/539599

Do we still want to deal with CTRL+C differently is daemon mode is running?
Could use this to completely overhaul how signals are processed -- which should probably happen, anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant