I'm using python to manage some simulations. I build the parameters and run the program using:
pipe = open('/dev/null', 'w')
pid = subprocess.Popen(shlex.split(command), stdout=pipe, stderr=pipe)
My code handles different signal. Ctrl+C will stop the simulation, ask if I want to save, and exit gracefully. I have other signal handlers (to force data output for example).
What I want is to send a signal (SIGINT, Ctrl+C) to my python script which will ask the user which signal he wants to send to the program.
The only thing preventing the code to work is that it seems that whatever I do, Ctrl+C will be "forwarded" to the subprocess: the code will catch it to and exit:
try:
<wait for available slots>
except KeyboardInterrupt:
print "KeyboardInterrupt catched! All simulations are paused. Please choose the signal to send:"
print " 0: SIGCONT (Continue simulation)"
print " 1: SIGINT (Exit and save)"
[...]
answer = raw_input()
pid.send_signal(signal.SIGCONT)
if (answer == "0"):
print " --> Continuing simulation..."
elif (answer == "1"):
print " --> Exit and save."
pid.send_signal(signal.SIGINT)
[...]
So whatever I do, the program is receiving the SIGINT that I only want my python script to see. How can I do that???
I also tried:
signal.signal(signal.SIGINT, signal.SIG_IGN)
pid = subprocess.Popen(shlex.split(command), stdout=pipe, stderr=pipe)
signal.signal(signal.SIGINT, signal.SIG_DFL)
to run the program but this gives the same result: the program catches the SIGINT.
Thanx!
I resolved this problem by creating a helper app that I call instead of creating the child directly. This helper changes its parent group and then spawn the real child process.
I call this helper in the parent, passing the real child and its parameters as arguments:
I have to do this because my child app is not under my control, if it were I could have added the setpgrp there and bypassed the helper altogether.
POSIX says that a program run with execvp (which is what subprocess.Popen uses) should inherit the signal mask of the calling process.
I could be wrong, but I don't think calling
signal
modifies the mask. You wantsigprocmask
, which python does not directly expose.It would be a hack, but you could try setting it via a direct call to libc via ctypes. I'd definitely be interested in seeing a better answer on this strategy.
The alternative strategy would be to poll stdin for user input as part of your main loop. ("Press Q to quit/pause" -- something like that.) This sidesteps the issue of handling signals.
This can indeed be done using
ctypes
. I wouldn't really recommend this solution, but I was interested enough to cook something up, so I thought I would share it.parent.py
child.py
Note that this makes a bunch of assumptions about various libc structures and as such, is probably quite fragile. When running, you won't see the message "SIGINT from child!" printed. However, if you comment out the call to
sigprocmask
, then you will. Seems to do the job :)Combining some of other answers that will do the trick - no signal sent to main app will be forwarded to the subprocess.
The function:
Works well only if Popen is being called right afterwards. If you are trying to prevent signals from being propagated to the subprocesses of an arbitrary package, then the package may override this before creating subprocesses causing signals to be propagated anyways. This is the case when, for example, trying to prevent signal propagation into web browser processes spawned from the package Selenium.
This function also removes the ability to easily communicate between the separated processes without something like sockets.
For my purposes, this seemed like overkill. Instead of worrying about signals propagating, I used the custom signal SIGUSR1. Many Python packages ignore SIGUSR1, so even if it is sent to all subprocesses, it will usually be ignored
It can be sent to a process in bash on Ubuntu using
It can be recognized in your code via
The available signal numbers on Ubuntu can be found at /usr/include/asm/signal.h.