Re: command does not return
- From: "Robert Hajime Lanning" <robert.lanning@xxxxxxxxx>
- Date: Fri, 26 Dec 2008 11:29:58 -0800
The python script needs to fork into the background and close stdin, stdout and
stderr.
ssh <ip> "nohup mycommand < /dev/null > /var/log/my.log 2>&1 &"
On Fri, Dec 26, 2008 at 4:38 AM, Laurent Mimoun <mimounl@xxxxxxxxx> wrote:
Hello,
My environnement is Debian Etch, and the version of ssh is 4.3p2.
I wrote a command <mycommand> that starts a python program. This
program calls a blocking method on a gamin monitor that waits for file
system changes (new files, for exemple).
I had to launch this python program (in mycommand) with "nohup" and
"&" at the end of the line because if not, mycommand is blocked.
Then when I enter the distant machine by writing only 'ssh <ip>' and
after connection, <mycommand> + ENTER, it returns correctly (I can
continue to write thing without to have to do crtl+c).
But when I launch the command like this : 'ssh <ip> <mycommand>', it
doesn't return.
It is blocked and I have to do ctrl+c to unblock. Furthermore, the
python program is correctly running on the distant machine.
Do you have any idea why 'ssh <ip> <mycommand>' is blocked ?
--
And, did Galoka think the Ulus were too ugly to save?
-Centauri
- References:
- command does not return
- From: Laurent Mimoun
- command does not return
- Prev by Date: command does not return
- Next by Date: running shell command through ssh tunnel
- Previous by thread: command does not return
- Next by thread: running shell command through ssh tunnel
- Index(es):
Relevant Pages
|