I've already written about tentakel tool and shell script hack to run a single command on multiple Linux / UNIX / BSD server. This is useful to save time and run UNIX commands on multiple machines. Linux.com has published an article about a new and better tool called pssh:
If you want to increase your productivity with SSH, you can try a tool that lets you run commands on more than one remote machine at the same time. Parallel ssh, Cluster SSH, and ClusterIt let you specify commands in a single terminal window and send them to a collection of remote machines where they can be executed.
Featured Articles:
- 20 Linux System Monitoring Tools Every SysAdmin Should Know
- 20 Linux Server Hardening Security Tips
- Linux: 20 Iptables Examples For New SysAdmins
- My 10 UNIX Command Line Mistakes
- 25 PHP Security Best Practices For Sys Admins
- The Novice Guide To Buying A Linux Laptop
- Top 5 Email Client For Linux, Mac OS X, and Windows Users
- Top 20 OpenSSH Server Best Security Practices
- Top 10 Open Source Web-Based Project Management Software
Facebook it - Tweet it - Print it -
We're here to help you make the most of sysadmin work. So, subscribe!
{ 8 comments… read them below or add one }
Take a look at Dancer’s shell, too.
Hi guys,
I’ve tried running these versions of pssh on RHEL 5.2:
pssh-1.2.2-1.el4.rf.noarch.rpmpssh-1.2.2-1.fc3.rf.noarch.rpm
pssh-1.2.2-1.rh9.rf.noarch.rpm
pssh-1.4.0-1.fc10.noarch.rpm
pssh-1.4.3-1.noarch.rpm
The older versions install but say
Traceback (most recent call last):File "/usr/bin/pssh", line 21, in ?
from basethread import BaseThread
ImportError: No module named basethread
The latest version doesn’t install
error: Failed dependencies:python(abi) = 2.5 is needed by pssh-1.4.3-1.noarch
Any ideas?
Thanks
I am also getting the same error on RHEL4 any success?
error: Failed dependencies:
python(abi) = 2.5 is needed by pssh-1.4.3-1.noarch
installing version pssh-1.2.2-1 is OK
Hey !!
I want to use pssh –options (-O) to add my key-file path and StrictHostKeyChecking=no
How ca n i do it ??
does anyone faced tty alocation within pssh?
being more specific pseudo-tty allocation …something like
ssh -t commandThatRequeriesTtyinstead of this “Parallel Distributed shell” (pdsh) is the good option.
PSSH is a bit typical to configure.