jackaraz jackaraz - 24 days ago 4x
Python Question

Terminating a program within a time frame through python

I'm running a fortran code from a python script which sometimes takes a while to run. Thus I'm limiting the run time with a code taken from this link:

def timeout(func, args=(), kwargs={}, timeout_duration=15, default=1):
import signal

class TimeoutError(Exception):

def handler(signum, frame):
raise TimeoutError()

# set the timeout handler
signal.signal(signal.SIGALRM, handler)
result = func(*args, **kwargs)
except TimeoutError as exc:
result = default

return result

I'm basically putting another function (partly below) in to this one (above) to run fortran code as:

subprocess.check_output('./../bin/SPhenoUMSSM ../UMSSM/LH_out_'+mod+' > SPheno_log_'+mod, shell=True)

However I realised that when fortran code takes more than 15 seconds, which is the boundary in timeout function, it leaves in the core and executes other one in the for loop which creates dump in my cores. In order to prevent that, I wanted to use
since it gives me pid to terminate the job in the core, but I need to wait for the process to be executed as well, like
does. Thus I was wondaring if there is a way to combine popen and check_output properties to wait until job is done within 15 seconds and if its not just terminates that.


Not the most sophisticated piece of code in the world but it may be useful.

import subprocess, time
x = subprocess.Popen(['sleep', '15'])
polling = None
i = 0
while polling == None:
    polling = x.poll()
    i +=1
    if i > 15: break
if polling == None:
        print "Time out - process terminated" # process terminated by kill command
    except OSError:
        print "Process completed on time" # process terminated between poll and kill commands
    except Exception as e:
        print "Error "+str(e) # kill command failed due to another exception "e"
    print "Process Completed after "+str(i)+" seconds"

Edit: Problems with kill not appearing to function.
Try using os.kill(x.pid, signal.SIGKILL) rather than SIGTERM.
I believe that SIGTERM asks the process to close down cleanly, rather than terminate immediately. Not knowing what drives the fortran script, it's difficult to know what the terminate signal does. Perhaps the code is doing something.
For example:
if I ran a shell script as follows:

trap "echo signal" 15
sleep 30

and sent it kill -15 pid_number, it would not print "signal" until the sleep had terminated after 30 seconds, whereas if I issued kill -9 pid_number it would terminate immediately with nothing printed out.

The short answer, is I don't know but I suspect that the answer lies within the script running the fortran code.


Note: In order to successfully run x.kill() or os.kill() or subprocess.call('kill '+ str(x.pid), shell=True), shell option in x needs to be False. Thus one can use

import shlex
args = shlex.split(ARGS HERE) 
x = subprocess.Popen(args) # shell=False is default

But also note that if you want to write the output to a log file by using ... >& log_file it wont work since >& is not an valid argument for your script but for your shell environment. Thus one needs to use only arguments that are valid for the script that python runs.