use of current on production systems

Hello,

I am tired of manually updating 20+ red hat servers.  I have looked 
around to see what is available and current seems to make a lot of 
sense: don't bother with client side software, lets red hat worry about 
that and just implement a solid server for up2date.  However, I am still 
REAL nervous about letting some automated processes get updates from a 
server and then manually update/install them.  The system I have in 
place now (a few shell scripts and wget) basically allows me to update 
stuff but I still do the final install by hand.  I realize up2date has 
gone through several versions, but I am still skeptical.  If these 
systems go down, it is my @#% in a vice in a major way - it will be 
painful.  The problem is that the sys admin stuff is distracting me from 
software development so I want to automate it a little more.  How many 
people on this list have a high level of confidence in both the security 
and reliability of the current/up2date combination?  Also, can kernel 
updates be cancelled?  I checked the up2date man page but there was no 
mention of it here.  Obviously, I could just not make those RPMs 
available for that given channel, but I would like to just mirror 
updates from Red Hat - which will download them.  Suppose I could just 
filter those out - anyone else know how kernel updates are handled?


-- 
Contact Designs <http://www.contactdesigns.com/contact/index.html>
http://www.contactdesigns.com
Web Development, Hosting, eCommerce, Online Marketing