[rhn-users] Patching Red Hat servers

[Riley, Liz (ACHE)]

The approach I had to take was as we build all our linux servers the
same, build another, and have it download all the patches come towards
the end of the quarter, test it, and then as I set it to keep all the
rpms, you can just do rpm -U * after copying the rpms (to be honest I
cheated and rolled it into a new rpm, which rolls out all the rpms and
installs it and logs any errors etc)..

  _____ 

From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com]
On Behalf Of West, Brian
Sent: 17 July 2006 20:00
To: rhn-users at redhat.com
Subject: [rhn-users] Patching Red Hat servers


We have recently introduced Linux into our environment and so I'm
wondering how others are handling the process of patching systems ?

It seems that RedHat Satellite Server would do it but for less than 10
servers it's a very expensive solution and one that our company won't
buy. If I understand Proxy Server correctly that only avoids a server
making a direct connection to RHN but rather to some other system.

Isn't there a method to simply download all patches for a given
distribution like RHEL 4 for AMD64 on a quarterly basis and use that as
a standard patch set ?

We basically want to use a standard patch set in a test, User Acceptance
and finally Production environment.


Thanks,

Brian.



______________________________________________________________________
CAUTION: This message was sent via the Public Internet and its
authenticity cannot be guaranteed.

______________________________________________________


******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************