Martin Guy via cfarm-users <cfarm-users@lists.tetaneutral.net> writes:
>Funny you should ask. I just implemented a set of scripts to perform >operations on all compile farm machines including installing build >dependencies under $HOME, configuring with different flags on some >architectures, compiling a prog and running its regression test suite >everywhere. Very useful, thanks, and it's written in bash and sed rather than a semi- custom scripting language, that gets my grunt of approval. try.sh looks like what I'm after, however (question for the cfarm maintainers) how does it handle repeated SSH connections? I was hoping to open one SSH connection, run a sequence of commands, then disconnect, in order to avoid hammering the servers with repeated SSH handshakes. In more general terms, I was looking for a way to automate the current manual process of ssh to server, upload, configure, make, make test, etc on each server. So there'd be no additional stress on the servers, just less typing to do. Peter. _______________________________________________ cfarm-users mailing list cfarm-users@lists.tetaneutral.net https://lists.tetaneutral.net/listinfo/cfarm-users
