≡ Menu

CentOS / RHEL Configure Yum Automatic Update Retrieval and Installation

The yum command line tool is used to install and update software packages under RHEL / CentOS Linux server. I know how to apply updates using Get nixCraft in your inbox. It's free:

  • cod3fr3ak May 19, 2009, 2:38 pm

    Good info. Thanks!

  • Marcus Moeller May 19, 2009, 4:29 pm

    This is where yum-updatesd is for. Please take a look at:


    for configuration parameters. Updates will automatically be applied with:

    do_update = yes

    Best Regards

  • Patrick May 19, 2009, 7:22 pm

    As Marcus said, yum-updatesd already does this !
    And as it’s not yet clearly said, auto updating is not recommended at all on production servers !!!
    Only do this on test or dev servers… or your linux desktop.
    Best regards

  • yum-check May 25, 2009, 6:20 am

    I use script called yum-check from CentOS wiki. It works great, its called from cron.daily and if there is a updates, send a mail to me. You can set only notify, download or direct download and install updates.


  • sys01admin September 13, 2010, 6:47 pm

    True, yum-updatesd already does handle ad hoc updates defined by the run_interval and updaterefresh intervals. My question is how do you define a specific time for updates. e.g. in production you want all servers to update say Friday, 3:00am, or nightly at 2:00am. Apart from cron how is that done?

    • nixCraft September 13, 2010, 7:22 pm

      You have three options:
      1) Write your own tool and push updates on all hosts using custome programming and cron jobs.
      2) Use patch managment software such as PatchLink Update Server, Novell ZENworks Linux Management, RHEL satellite/Spacewalk etc.
      3) Use other open source system management tools such as Chef, Puppet, and, Cfengine.

      • sys01admin September 15, 2010, 1:23 pm

        Thanks Vivek, very helpful!

        • Florian Heigl May 2, 2015, 6:31 pm

          Ah, so after everyone pointing to yum-updatesd, once the point of not blindly rebooting at random times comes up we suddenly agree that the top example of doing it from cron actually wasn’t so stupid at all.

          Internet, full of wonders.

  • Antonio September 8, 2011, 10:43 am

    Why -R is equal to 120? Why yum will wait 120 minutes to start ?

    • Jason August 12, 2015, 3:49 pm

      The -R flag makes yum wait a random number of minutes between 0 and the value before starting. The reason it is in there is so when a million people copy this script onto their machines, they don’t all attempt to hit the Redhat update servers at exactly 12:00 GMT every night and DOS them. This spreads the load out.

  • Mykolas OK November 9, 2011, 5:36 pm

    Patric says: updating is not recommended at all on production servers

    I would like to make critical updates (bug fixes) on my production servers daily.
    Is it not good idea?

    How to organize it without updating packages to new versions?

    Thank you for comments.

  • Annegret February 7, 2012, 3:26 pm

    Bravo!!! You have taken a farufel task and made it come out smooth. WELL DONE TUTORIAL!

  • Christian April 2, 2012, 6:59 am

    Nice tutorial. BTW, why isn’t it recommended to auto-update? I can choose the repos and sources I want to install, and if I have a server for which security is critical – why not keep it up to date?
    Of course, external sources/repos and Alpha/Beta/RC software isn’t a good idea on those – but if I stick to the original repos, then what is in the way of having a cron job do the work.
    BTW, I think the -R 120 option is for having yum wait in case that it cannot perform its job right away. But feel free to correct me, if I am wrong.

  • guest007 March 7, 2013, 2:05 am

    Updating automatically is not recommended on production servers because you do not know if it will break anything in your application, there are many instances where due to a patch you might need to update your application.

    As to how do organizations do it, you have a patching cycle where you would apply updates to QA/test environment and have QA regress to make sure there are no issues. Next you apply same updates to staging and perform QA. Lastly you go through change control and apply updates to production (usually do half the farm), and QA. After half the production farm is updated and performing without issues, go ahead and patch the remaining servers. At least this is how it is done in 24x7x365 environments.

  • kubrick April 24, 2013, 9:39 am

    If you want automatic updates in CentOS 6, install this package:
    yum install yum-cron


Leave a Comment

You can use these HTML tags and attributes: <strong> <em> <pre> <code> <a href="" title="">

   Tagged with: , , , , , , , , , , , ,