Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin3!goblin.stu.neva.ru!newsfeed3.funet.fi!newsfeed2.funet.fi!newsfeeds.funet.fi!news.cc.tut.fi!not-for-mail From: Anssi Saari Newsgroups: comp.lang.python Subject: Re: How to program in Python to run system commands in 1000s of servers Date: Thu, 07 Apr 2011 22:14:17 +0300 Lines: 14 Message-ID: References: <0bb6311b-135a-4458-9258-1eca3be3cd31@q12g2000prb.googlegroups.com> NNTP-Posting-Host: pepper.modeemi.fi Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.cc.tut.fi 1302203657 2620 2001:708:310:3430:203:baff:fe7d:42dd (7 Apr 2011 19:14:17 GMT) X-Complaints-To: abuse@tut.fi NNTP-Posting-Date: Thu, 7 Apr 2011 19:14:17 +0000 (UTC) User-Agent: Gnus/5.101 (Gnus v5.10.10) Emacs/21.3 (usg-unix-v) Cancel-Lock: sha1:ElZVlYuy91LCnEKhrsHCMOCuN5U= Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:2801 Chris Angelico writes: > Depending on what exactly is needed, it might be easier to run a > separate daemon on the computers, one whose sole purpose is to do the > task / get the statistics needed and return them. Then the Python > script need only collect each program's returned response. Those would still need to be deployed somehow to the thousands of machines though. I realized after posting that something like pexpect might work for stuffing the keystrokes needed to root login via ssh to all machines and such... If that's what he needs to do, since it wasn't very clear.