Hi,
Personally, I would avoid the entire rsh/rlogin/etc suite and use ssh (or similar). Other than that, I can see an issue with the script that don't appear to be an issue in your environment:
- The script contacts servers A, B and C.
- Server A completes the task, but server B doesn't respond... then Server C may not complete the task in the 'time window' if at all.
- It would probably be better to spawn off the tasks to each individual server then display the output sequentially when the tasks are completed. That way the time is dramatically decreased.
- This is assuming that B & C do not rely on the output of A.
You deserve the ++ I gave ya though :)
Jason L. Froebe
Team Sybase member No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1
| [reply] |
Hi Jason,
We actually did move Multex away from rsh to ssh recently. It's much slower, but that's the price you pay, I guess.
| [reply] |