I'm wondering if this is the correct way to execute a system process and detach from parent, though allowing the parent to exit without creating a zombie and/or killing the child process. I'm currently using the subprocess module and doing this...
os.setsid() os.umask(0) p = subprocess.Popen(['nc', '-l', '8888'], cwd=self.home, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
os.setsid() changes the process group, which I believe is what lets the process continue running when it's parent exits, as it no longer belongs to the same process group.
Is this correct and also is this a reliable way of performing this?
Basically, I have a remote control utility that communicate through sockets and allows to start processes remotely, but I have to ensure that if the remote control dies, the processes it started continue running unaffected.
I was reading about double-forks and not sure if this is necessary and/or subprocess.POpen close_fds somehow takes care of that and all that's needed is to change the process group?
Thanks.
Ilya
popen
on Unix is done using fork
. That means you'll be safe with:
Popen
in your parent processWhen the parent process exits, the child process is inherited by the init
process (launchd
on OSX) and will still run in the background.
The first two lines of your python program are not needed, this perfectly works:
import subprocess p = subprocess.Popen(['nc', '-l', '8888'], cwd="/", stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
I was reading about double-forks and not sure if this is necessary
This would be needed if your parent process keeps running and you need to protect your children from dying with the parent. This answer shows how this can be done.
How the double-fork works:
os.fork()
Popen()
which launches the long running processPopen
process is inherited by init
and runs in the backgroundWhy the parent has to immediately exit? What happens if it doesn't exit immediately?
If you leave the parent running and the user stops the process e.g. via ctrl-C
(SIGINT
) or ctrl-\
(SIGQUIT
) then it would kill both the parent process and the Popen
process.
What if it exits one second after forking?
Then, during this 1s period your Popen
process is vulnerable to ctrl-c etc. If you need to be 100% sure then use the double forking.
For Python 3.8.x, the process is a bit different. Use the start_new_session
parameter available since Python 3.2:
import shlex import subprocess cmd = "<full filepath plus arguments of child process>" cmds = shlex.split(cmd) p = subprocess.Popen(cmds, start_new_session=True)
This will allow the parent process to exit while the child process continues to run. Not sure about zombies.
The start_new_session
parameter is supported on all POSIX systems, i.e. Linux, MacOS, etc.
Tested on Python 3.8.1 on macOS 10.15.5
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With