On Fri, 28 Nov 2008, Eric F Crist wrote: > I think drue's suggestion of clusterssh was probably the most helpful... > Just my two cents. A couple more cents - like a reason -- wouldn't hurt, but thanks for reminding us about the ClusterSSH suggestion. I just looked it up: http://clusterssh.wiki.sourceforge.net/FAQ I'm not sure of how certain aspects work, but it looks to me like the ssh-keygen is something he'll have to do for ClusterSSH unless he wants to type 10 passwords every time. After that he gets to see 10 windows at once all doing the same thing -- for no good reason? -- and he types commands instead of executing scripts. That might be better, but I don't see how. It sounds like it is more similar to what he is used to with PuTTY though. On the other hand, if his task were more ad hoc and less automated, I can see where ClusterSSH would be handy. But would it still be a good solution for 100 servers? Or even 30 servers? Mike > On Nov 28, 2008, at 2:35 PM, Mike Miller wrote: > >> On Fri, 28 Nov 2008, Kevin Lombardo wrote: >> >>> On Fri, Nov 28, 2008 at 1:11 AM, Mike Miller <mbmiller at taxa.epi.umn.edu> >>> wrote: >>>> On Thu, 27 Nov 2008, Kevin Lombardo wrote: >>>> >>>>> On my Windows box, I have a program called Putty Command Sender, which >>>>> will execute a command on all existing Putty instances, or a subset of >>>>> them based on a filter. >>>>> >>>>> Is there a good way to do this in Gnome? Whether with gnome-terminal >>>>> or another term program? >>>> >>>> >>>> Would you mind telling us what you use it for? I'm curious. Also, if >>>> I knew what you were doing, I might come up with an idea. >>> >>> >>> I have 10 servers which I deploy applications on. I just copy the file >>> to the server, validate the md5sum, rm the old application, and untar >>> the new one. >> >> OK. Here's something I haven't used myself, but I think it is the sort of >> thing you'll be wanting to do. You can set up ssh so that you can log in >> securely without a password. Read about "ssh-keygen" and related >> programs. There are man pages and there should be plenty of step-by-step >> guides on the web (maybe someone else on this list will know which are >> best). You can then use scripts to run commands on the remote systems: >> >> ssh system1 "command args filenames" >> ssh system2 "command args filenames" >> ssh system3 "command args filenames" >> >> I think you will discover that this makes your life a lot easier than use >> of PuTTY on Windows. You can even do this kind of stuff with >> stdin/stdout: >> >> cat file.tgz | ssh system "rm oldfiles ; cat - > file.tgz ; md5sum file.tgz >> ; tar zxf file.tgz ; whatever" >> >> The stdout from md5sum goes to you on the local machine. I have tested >> this and it works. I had to enter my password though, but you can set it >> up with keygen and avoid that step. >> >> Using a bash script, you can make it so that you maintain a list of system >> names in a file, then tell bash that for every system in the file it >> should do the following... >> >> Mike >> >> _______________________________________________ >> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >> tclug-list at mn-linux.org >> http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > --- > Eric Crist > > >