RE: automated installation of rpm/app on a number of client machines



hi tom...

what you suggested is more or less what i had been thinking about...

as to the config file/mods, i might also create a script that takes a
midified file, and simply does a network wide cp/mv to replace the client
file, with the updated config file... or some kind of auto bash script to
modify the client config file on the client system...

-bruce


-----Original Message-----
From: Tom Brown [mailto:tom@xxxxxxxx]
Sent: Friday, August 18, 2006 9:00 AM
To: bedouglas@xxxxxxxxxxxxx; For users of Fedora Core releases
Subject: Re: automated installation of rpm/app on a number of client
machines



there appears to be some kind of mis-understanding regarding my question..

if i have 50 systems.. i'm trying to figure out how to automate the
process
of installing the rpms across the 50 systems, so i don't have to do it
manually. i was also saying that the install process might also involve
creating of users/modifying config files...

if you're implying that i could 'modify' the rpm file, so that the
invoking
of the rpm would perform these functions, then ok.. maybe.

i'm trying to find out if there's an automated/scripting method for this
kind of purpose. has anyone actually done this kind of automated action,
and
if you have, cna you tell me how you did it...

make sure root keys are setup on your hosts so your 'master' box can ssh
into the others without a password.

then

#!/bin/bash
HOSTNAMES=`cat machinelist.txt`

for i in $HOSTNAMES
do
ssh $i 'rpm -i /path/to/some.rpm'

done

that will install the rpm on each host listed in machinelist.txt but of
course the rpm must be on the system first so either have it on a share or

#!/bin/bash
HOSTNAMES=`cat machinelist.txt`

for i in $HOSTNAMES
do
scp some.rpm $i:
ssh $i 'rpm -i /path/to/some.rpm'

done

would copy it over to the host and then install it

HTH

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



Relevant Pages

  • Re: SBS03 - ISA 2004 re-install - Apply SP, backup, and FW clients
    ... Thanks again Cris- I think the safest route since the config is from SP3 is ... most clients and that must be why the minority had a FW client running. ... For my customers I install the FW client and then remove proxy info ... Install ISA 2004, apply SP3, then import backup config. ...
    (microsoft.public.windows.server.sbs)
  • Re: How install Access app on client PCs ?
    ... To automate the initial distribution you'd use VB Script or something ... > installing on 50-100 client PC's. ... > initial install and when versions change. ...
    (microsoft.public.access.gettingstarted)
  • Re: Courier-imap authentification
    ... I run both of these but my initial install and config was done years ago and ... setting up webmail but never did (most webmail apps use maildir format). ... Please note that my config is old and simple - YMMV! ... i've open my 993 port on my gate to have access to it. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Courier-imap authentification
    ... I run both of these but my initial install and config was done years ago and ... setting up webmail but never did (most webmail apps use maildir format). ... Please note that my config is old and simple - YMMV! ... i've open my 993 port on my gate to have access to it. ...
    (comp.unix.bsd.freebsd.misc)
  • [opensuse] xinet.conf configuration "preference", "question"...
    ... <list of all xinet services specifying disabled or enabled> ... <then list of all services in config file to specify params ... each service in separate file allowing services ... Install is as straight-forward as WB, ...
    (SuSE)