English Spanish
You would replace root with an actual email address to which you want the report sent, and localhost with an actual address of a SMTP server. This change will mean that after dnf-automatic runs, it will email you information about available updates, a log about downloaded packages, or installed updates according to settings in `automatic.conf`.
You update from other third party DNF repositories besides Fedora (core, extras, legacy), repositories which may conflict in versioning schemes for the same packages.
You should then edit the configuration. Descriptions of the options are contained in the conf file `/etc/auter/auter.conf`.
Your environment requires meticulous change-control procedures.
You must decide whether to use automatic xref:dnf.adoc[DNF] updates on each of your machines. There are a number of arguments both for and against automatic updates to consider. However, there is no single answer to this question: it is up to the system administrator or owner of each machine to decide whether automatic updates are desirable or not for that machine. One of the things which makes one a good system administrator is the ability to evaluate the facts and other people's suggestions, and then decide for oneself what one should do.
You installed custom software, compiled software from source, or use third party software that has strict package version requirements.
You installed a custom kernel, custom kernel modules, third party kernel modules, or have a third party application that depends on kernel versions (this may not be a problem if you exclude kernel updates, which is the default in Fedora `dnf.conf` files). (See also https://bugzilla.redhat.com/show_bug.cgi?id=870790[bug #870790] - you may need to modify the base section to add `exclude=kernel*`.)
You do not have any irreplaceable data on the machine, or have proper backups of such data.
You can still use `download_updates` and `apply_updates` settings from inside `/etc/dnf/automatic.conf`.
You can monitor updates availability automatically by email after modifying the dnf-automatic configuration file (usually `/etc/dnf/automatic.conf`).
You can live without remote access to the machine until you can get to its physical location to resolve problems.
You are unlikely to apply updates manually for whatever reason(s).
Yet another thing to consider if not using automatic updates is to provide your machine with some other forms of protection to help defend it of any attacks that might occur before updates are in place. This might include an external firewall, a host-based firewall (like iptables, ipchains, and/or tcp wrappers), not performing dangerous tasks on the computer (like browsing the web, reading e-mail, etc.), and monitoring the system for intrusions (with system log checkers, IDS systems, authentication or login monitoring, etc).
Why use automatic updates?
While no one can determine for you if your machine is a good candidate for automatic updates, there are several things which tend to make a machine a better candidate for automatic updates.
While no one can determine for you if your machine is a bad candidate for automatic updates, there are several things which tend to make a machine a worse candidate for automatic updates.
Unwanted side effects. Some packages can create annoying side effects, particularly ones which have cron jobs. Updates to base packages like openssl, openldap, sql servers, etc. can have an effect on many other seemingly unrelated packages.
To make auter run immediately without waiting for the cron job to run, for example for testing or debugging, you can simply run it from the command line:
to enable and start the `systemd` timer.
This problem can be fixed by modification of the timer of dnf-automatic using the description on the xref:understanding-and-administering-systemd.adoc[Understanding and administering systemd] page.