rsh is pretty similiar to rexec. The main difference is that rexec uses
$HOME/.netrc to determine access and rsh uses $HOME/.rhosts
The command would be
rsh server1 <command>
Just like rexec.
A sample .rhosts file would be
server1 user1
server2 user2
and so on.
If you run SP you can kerberize your user which is much more secure and you
won't need (and shouldn't use) .rhosts
And although we've all seen it, this is a big no-no
server1 root
I'd setup a restricted user to do this.
--
Tom Walker
Tom Walker
Technical Support Analyst
EMI Recorded Music, NA
212-408-8311
> -----Original Message-----
> From: Warren, Matthew James [mailto:matthewjames.warren AT EDS DOT COM]
> Sent: Friday, November 30, 2001 9:43 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Scripted synchronised backups..
>
>
> Hello TSM'ers,
>
> This is one for you unix scripting people out there.
>
> I am unable in our environment to test the kinds of commands needed to
> achieve this, but we have a customer who wishes to perform
> backups on 5
> machines, controlled from one machine.
>
> So, a script would execute on one machine, remotely invoke a
> backup script
> on each of the other machines and then wait untill those scripts have
> finished before continuing.
>
> My initial idea would be to use something like a series of
> rexecs placed
> into the background, followed by a wait to wait for these
> scripts to return.
>
> (pseudo-Ksh-code)
>
> pre-backup stuff
>
> rexec host backup.sc &
> rexec host backup.sc &
> etc..
> wait
>
> post backup stuff
>
>
>
> Our customer though does not hjave rexec available, and woudl like to
> perform somthing similar maybe using rsh ?
>
> My scripting is Ok, but I have not done much with remote
> shells / commands
> etc.. so I wouldnt know how they behaved without testing it
> out a few times
> myself, which I can't do atthe moment.
>
>
> Does anyone have any Ideas or do anything similar?
>
> Thanks,
>
> Matthew Warren.
> EDS Core Infrastructure.
> Wavendon Tower.
> Milton Keynes.
> GZPTXW.
>
This e-mail including any attachments is confidential and may be legally
privileged. If you have received it in error please advise the sender
immediately by return email and then delete it from your system. The
unauthorized use, distribution, copying or alteration of this email is strictly
forbidden.
This email is from a unit or subsidiary of EMI Recorded Music, North America
|
