This might be a bit low-tech, but if this is machine 'A' that is executing 20 (or so) commands determined by machine 'B' one thing you could do is: Create a script on 'B' Create a cron job on 'A' that pulls the script from 'B' and executes it.
There are some downsides - you need to ensure that nobody can monkey with the script on 'B'. You need to make sure that no other machine can impersonate 'B'. An alternate approach is Expect. I've used this as a hammer a few times and it has always nailed the problem. Low points for elegance though (hey - it is a hammer right?) On Wed, 2009-04-08 at 10:34 -0600, Greg Saunders wrote: > Hi all, I'm looking for the best way to run a remote process. SSH with > keys? "ssh [email protected] remoteprocess" > > Is there a better way, especially if you have to execute 20 remote > commands each time and those commands are determined on the fly and > not known ahead of time. > > Thanks! > Greg > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
