> I don't get the "it's not applicable in this case" part. The way you start > them on web2py is the same one you can use with the scheduler....
Does not seem applicable because does not address the problem of dependent child processes. > Starting child processes from webserver main process is never safe because > of the problem you're facing. The second you kill the webserver process (or, > in more advanced webserver, when it realizes it's a process lasting too > long) the child process is killed too (a webserver is "made" for responding > quickly, so advanced ones try to free up "hanging" resources). Exactly, so am trying to figure out how the process can be detached. > However, this is not a problem on web2py per se, but on how python handles > processes spawned. If you can't get a normal python script to launch a > process that is not killed when the main python program is killed, then > web2py can't really help with that. I'm after a python solution, not web2py specific. Sorry should have clarified that. I thought someone else may have faced the same problem here. > If you just need to launch them and never communicate with > those again, did you try with > import subprocess > subprocess.Popen([whatever], stdout=subprocess.PIPE, stderr=subprocess.PIPE, > stdin=subprocess.PIPE) Unfortunately this is still a child process so faces original problem. Using a separate service like at command is a good idea, however I need to know the process ID. --
