Behaviour of subprocess.Popen, ssh and nohup I don't understand

Adriaan Renting renting at
Fri Apr 1 01:01:19 CEST 2011


I have a problem that a background process that I'm trying to start with
subprocess.Popen gets interrupted and starts waiting for input no matter
what I try to do to have it continue to run. It happens when I run it
with nohup in the background.
I've tried to find a solution searching the internet, but found none.
I've written a small test script that reproduces the problem and hope
maybe here there is someone who can tell me what's going wrong. Any
suggestions are welcome.

(renting)myhost> cat
# script to test subprocess problem
import subprocess, sys, time

for f in range(3):
  command = ["ssh", "-T", "localhost", "uptime"]
  comm = subprocess.Popen(command, shell=False, stdin=None,
stdout=subprocess.PIPE, stderr=subprocess.STDOUT, close_fds=True)
  print  '1'
  if comm.returncode:
    print "error: %i" % (comm.return_code)
    print  '2'
    (output, output2) = comm.communicate(input=None)
    print output
    print output2 
  print  '3'

(renting)myhost> python --version
Python 2.5.2

(renting)myhost> nohup ./ -O2 &
[1] 15679

(renting)myhost> 1
 22:40:30 up 24 days,  7:32,  1 user,  load average: 0.00, 0.00, 0.00


[1]  + Suspended (tty input)         ./ -O2
(renting)myhost> fg
./ -O2

 22:40:35 up 24 days,  7:32,  1 user,  load average: 0.00, 0.00, 0.00

 22:40:56 up 24 days,  7:32,  1 user,  load average: 0.00, 0.00, 0.00



Now as you can see, it suspends on the second time through the for loop,
until I bring it to the foreground and hit .
What you don't see, is that I make it do this by pushing the arrow keys
a couple of times. The same happens when I would exit the shell, despite
it running with nohup.
I don't need to exit to make it suspend, any combination of a few random
keystrokes makes it do this. It seems depending on the timing though,
during the sleep(3) it seems to ignore me, only when subprocess is
actually running will it suspend if I generate keystrokes.
If the ssh command is executed without -T option it suspends directly,
so I think it's related to the ssh command. I log in with a
public/private key pair to avoid having to enter a password.

Any suggestions are welcome,


Adriaan Renting

More information about the Python-list mailing list