This all depends on what applications you have on your server and how secure your border gateway is.
If you are in a reasonably secure environment and you are monitoring CERT's for major vulnrabilities (and responding to them by testing and applying patches!) then you may get away with once a week - once a month.
But if you have little security then (as Red Hat release sometimes 2-3 bug fixes & security patches per week) may be you should run it more regularly.
My advice is to allways test any updates in a controled environment before aplying onto a production environment.
Register on redhat network and you will be notified whenever a new patch pertanant to your system is avalible, it is free to register but you do need to re-register with a quick survey every 3 months (I think).
I would think carefully before diving in and using "any" automatic update program. You need to be sure that you first take a reliable backup of your system (so if all goes wrong you have a way back) and that you are able to control whatever tool you use so you only update what "YOU" want updated!
Your developers will not be happy bunnies if you introduce incompatibilities by blasting the server with new binaries willy-nilly!
looks interesting , but the "quick start" says nothing about “Run A Report Of What’s Required But Do Not Install”, Definitely worth a look though.
"I would think carefully before diving in and using "any" automatic update program."
Thats why I like autoupdate. It puts you in control of the update process. I use it to auto download the updates, tell me what available, then I decide what updates to actually install, and when to do it.
I agree that up2date might be dangerous. It puts RedHat in charge of your system.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.