YUM CRON RHEL7: Configure automatic updates.

Presentation

The yum-cron package provides a convenient way to check for, download and apply updates automatically.

Installation procedure

Install the yum-cron package:

# yum install -y yum-cron

Start the yum-cron service:

# systemctl start yum-cron

By default, the configuration of the yum-cron service is done through two files following exactly the same syntax:

  • /etc/yum/yum-cron.conf defines what is done once every day,
  • /etc/yum/yum-cron-hourly.conf defines what is done once every hour.

Still by default, no action in defined in the /etc/yum/yum-cron-hourly.conf file. Conversely, in the /etc/yum/yum-cron.conf file associated with daily actions, instructions are given to send a message on stdio (which means written into the /var/log/cron file) when any update is available (see update categories below), to download it without applying it.

Configuration syntax

In any of the two configuration files, configuration is defined through the following directives:

  • update_cmd = value specifies the category of upgrade where value can take:
    • default for yum upgrade,
    • security for yum –security upgrade,
    • security-severity:Critical for yum –sec-severity=Critical upgrade,
    • minimal for yum –bugfix upgrade-minimal,
    • minimal-security for yum –security upgrade-minimal,
    • minimal-security-severity:Critical for yum –sec-severity=Critical upgrade-minimal.
  • update_messages = yes/no defines whether a mail is sent when updates from the previously specified category are available.
  • download_updates = yes/no specifies whether these available updates need to be downloaded.
  • apply_updates = yes/no defines whether these available updates need to be applied.
  • random_sleep = 15 specifies the maximum time in minutes to randomly sleep preserving bandwidth and avoiding download storms.
  • emit_via = stdio/email/none defines what kind of message is used: stdio means written into the /var/log/cron file, email causes a mail to be sent, none doesn’t do anything.
  • email_from = root@localhost, email_to = root, email_host = localhost defines respectively when the message is a mail the originator’s email address, the recipient’s email address and the host to which the mail is sent.

Note: As the official CentOS repositories don’t provide any security metadata, update_cmd = default is the only option that works (see here for details). To get these security metadata, you will have to get them through this website. It is also possible to get CentOS security updates through the procedure provided by Casey Labs.

Source: Linuxaria’s website.

0 (0)
Article Rating (No Votes)
Rate this article
Attachments
There are no attachments for this article.
Comments
There are no comments for this article. Be the first to post a comment.
Full Name
Email Address
Security Code Security Code
Related Articles RSS Feed
UUIDs and Linux: Everything you ever need to know [Update]
Viewed 5067 times since Tue, Jul 17, 2018
systemd Auto-restart a crashed service in systemd
Viewed 3410 times since Fri, Jan 17, 2020
LVM: Remove a Filesystem / Logical Volume
Viewed 2723 times since Sat, Jun 2, 2018
Tcpdump Examples Linux
Viewed 6056 times since Fri, Nov 16, 2018
linux unix aix banner /etc/issue
Viewed 2120 times since Fri, Aug 3, 2018
Moving SSL Certificate from IIS to Apache
Viewed 2130 times since Mon, Feb 18, 2019
List of 10 Must Know Oracle Database Parameters for Database Administrator
Viewed 130185 times since Thu, Jun 21, 2018
ZFS: Remove an existing zfs filesystem
Viewed 2242 times since Sun, Jun 3, 2018
How to use yum-cron to automatically update RHEL/CentOS Linux 6.x / 7.x
Viewed 5235 times since Tue, Dec 4, 2018
How to deal with dmesg timestamps
Viewed 3721 times since Wed, Oct 3, 2018