Re: how to logon to 30+ machines and put a job run in background and then logout automatically in a script file?
From: Stephen Copp (scopp_at_ea.com)
Date: 09/30/03
- Previous message: Bryan Dongray: "Re: how to send control-break or ctrl-c signal to a background process?"
- In reply to: Bill Marcum: "Re: how to logon to 30+ machines and put a job run in background and then logout automatically in a script file?"
- Next in thread: Andreas Kahari: "Re: how to logon to 30+ machines and put a job run in background and then logout automatically in a script file?"
- Reply: Andreas Kahari: "Re: how to logon to 30+ machines and put a job run in background and then logout automatically in a script file?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 29 Sep 2003 19:25:01 -0700
Hi Bill,
I'm having a similar issue with 'ssh' asking for passwords everytime (once
would be fine). Could you please explain further on the following. I don't
quite understand what you mean by "public keys":
> By using public keys, you don't need to type the password.
> man ssh
> man ssh-copy-id
Also, is there anything to get around 'scp2' asking for passwords? Thanks.
-Stephen
"Bill Marcum" <bmarcum@iglou.com> wrote in message
news:oh9h41-6ge.ln1@don.localnet...
> On Fri, 26 Sep 2003 17:50:33 -0500, walala
> <mizhael@yahoo.com> wrote:
> > Dear all,
> >
> > I am facing a problem that needs your help... I need to run a simulation
in
> > part on about 30+ unix workstations, servers, etc. We use ssh here.
> >
> > Every time I need to do the following:
> >
> > ssh username@machinename1.xxx.xxx.xxx
> > nohub run_some_job_in_background &
> > logout
> > ssh username@machinename2.xxx.xxx.xxx
> > nohub run_some_job_in_background &
> > logout
> > ssh username@machinename3.xxx.xxx.xxx
> > nohub run_some_job_in_background &
> > logout
> >
> > the trouble was:
> >
> > a. The above script scheme did not work. after I typed in the password
for
> > the first login, it logged onto the first machine, and run .cshrc of
that
> > machine, and then stopped, without running my "nohub" and "logout"
command,
> > basically, it stopped there;
> >
> I think you mean "nohup", and couldn't you do it on one line, like
> ssh username@machinename "nohup run_some_job &"
>
> > b. Even if the scheme worked, there still has the trouble that everytime
I
> > need to type in password again and again for the 30+ machines...
> >
> By using public keys, you don't need to type the password.
> man ssh
> man ssh-copy-id
>
> > Can anybody give me help on how to fully streamline the whole process?
> >
> > Thanks a lot,
> >
> > -walala
> >
> >
>
>
> --
> Commander Spiral Pyjama Pseudo-Rhinocerous Feline Thingamajig Bill Marcum
> (the First)
> Ozy and Millie Name Generator http://heifong.phase.org/omname.php
- Previous message: Bryan Dongray: "Re: how to send control-break or ctrl-c signal to a background process?"
- In reply to: Bill Marcum: "Re: how to logon to 30+ machines and put a job run in background and then logout automatically in a script file?"
- Next in thread: Andreas Kahari: "Re: how to logon to 30+ machines and put a job run in background and then logout automatically in a script file?"
- Reply: Andreas Kahari: "Re: how to logon to 30+ machines and put a job run in background and then logout automatically in a script file?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
