| Tomer Filiba tomerfiliba.com |
Hi,I'm trying to use rpyc to run commands on remote servers.I am interested in sending back STDOUT/ERR responses to the client, and having the option of terminating the running command after a predefined timeout. I care less if its run async or not.
My problem is that Popen has blocking reads, and will also need to be terminated manually ? (It seems that if I use rpyc.timeout, although the client times out, the popen/command continues to run on the server).
I'm not much of a python programmer, however this is my only need.I also googled around, and tried hacking a fix myself, but was unsuccessful.Can you please tell me what needs to be done ? (or maybe hack up a solution yourself for me :)Toda.
I might be wrong here, but the call to proc.communicate() would be synchronous, so I could not terminate()/kill() it with a timeout (It would wait unter .communicate would finish).This is what seems to happen in my testing.
From: Tomer Filiba <tomer...@gmail.com>
To: Ido <ido2...@yahoo.com>
Cc: rpyc <rp...@googlegroups.com>
Sent: Saturday, 28 January 2012, 13:47
Subject: Re: problems with RPYC calling subprocess.Popen