On 09/22/2016 03:13 PM, Pete Travis wrote:
On Sep 22, 2016 12:49 PM, "bruce" <badouglas@xxxxxxxxx
<mailto:badouglas@xxxxxxxxx>> wrote:
>
> Hey guys.
>
> Trying to get my heads around something. I'm looking to automate a
process. Basically, I want to kick off/initiate a number of processes
on remote boxes. I've looked at different online sites, but I'm
missing something..
>
> I can ssh into the box, trivial.
> I know I can create a "screen" process, that allows me to then later
access the 'screen' session to see the progress of the action. And of
course I can access the screen and fire up my process.
>
> However, (and here's where I'm not getting how to do it) - I'd like
to be able to auto/programatically :
>
> ssh into the remote box
> create the screen session (with a name I define)
> access the screen session, and then fire up/start my process
>
> If I can figure out how to do all of this initially for a test, I
can of course roll out the rest of my tests...
>
> Hope this makes sense.
>
> (if someone has a chunk of code, or pointers to any code I can look
at, that would be great.)
>
> I suspect this is really trivial.
>
> Thanks again...
>
Do you need to interact with this automated process? If not, running
it as a oneshot service unit might be a better fit. I'm curious what
the thing does, and what led you to screen as a way of doing it.
--Pete
How about running a script that invokes rexec to all the remote machines
in question?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
