fab-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fab-user] Design pattern for launching a remote program that does not r


From: Paul Hoffman
Subject: [Fab-user] Design pattern for launching a remote program that does not return?
Date: Mon, 22 Apr 2019 11:24:02 -0700

Greetings. I use fabric in a testbed that launches commands on a particular remote computer. It works fine for
   c.run("/path/to/command")
when the command is a regular command like "hostname" or when it is a daemon that launches itself in the background.

But I now need to launch what is in essence a command-line program *even though I don't need to interact with the command line*. I will later kill that command using other stuff that works fine with daemons. For example (this is not what I really need to do):
   c.run("/usr/bin/ftp")
In this case, "run" never returns, which of course stops the outer Python program.

Is there a way in Fabric to say "launch this program and return immediately"? I am not seeing it in the invoke.runners.Runner doc, but I could be missing it.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]