What is your use case? It might be easier for you to describe the overall result you want, at a very high level. E.g. "I want the text printed out by running 'ls /var/www/' on my server, to end up in a local text file on my workstation's hard drive". Then we can tell you how best to accomplish that with Fabric.
-Jeff On Mon, Oct 18, 2010 at 1:27 PM, Jeff Honey <[email protected]> wrote: > The former would be nice but the latter would be a good start in the right > direction. When I looked in the API docs, I guess I wasn't real clear on what > happened to the command's output > > "run will return the result of the remote program’s stdout as a single > (likely multiline) string. This string will exhibit a failed boolean > attribute specifying whether the command failed or succeeded, and will also > include the return code as the return_code attribute." > > So, does this mean I can just open a file and simply redirect sys.stdout to > the file and I'll get what I'm looking for? > > -- > ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤ > ¤ kyoboku kazeoshi ¤ > ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤ > _______________________________________________ > Fab-user mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/fab-user > -- Jeff Forcier Unix sysadmin; Python/Ruby developer http://bitprophet.org _______________________________________________ Fab-user mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/fab-user
