English Spanish
If you want to disable auter from running, including from any cron job:
auter --disable
Alternatives to automatic updates
Scheduling updates
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.
Other methods of protection
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.
Even the general rule above has exceptions, or can be worked around. Some issues might be resolved through a special setup on your part. For example, you could create your own DNF repository on a local server, and only put in tested or trusted updates. Then use the automatic updates from only your own repository. Such setups, while perhaps more difficult to set up and maintain, can remove a large amount of risk otherwise inherent in automatic updates.
On a fresh install of Fedora 22 with default options, the dnf-automatic RPM is not installed. The first command below installs this RPM:
By default, dnf-automatic runs from the configurations in the `/etc/dnf/automatic.conf` file. These configurations only download, but do not apply any of the packages. In order to change or add any configurations, open the `.conf` file as the root user (or using `sudo`) from a terminal window.
Detailed description of dnf-automatic settings is provided on the https://dnf.readthedocs.org/en/latest/automatic.html[dnf-automatic] page.
Once you are finished with the configuration, execute:
systemctl enable --now dnf-automatic.timer 
The main advantage of automating the updates is that machines are likely to get updated more quickly, more often, and more uniformly than if the updates are done manually. We see too many compromised machines on the internet which would have been safe if the latest updates where installed in a timely way.
If all the above apply to your machine(s), then automatic updates may be your best option to help secure your machine. If not all the above apply, then you will need to weigh the risks and decide for yourself if automatic updates are the best way to proceed.
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 update from other third party DNF repositories besides Fedora (core, extras, legacy), repositories which may conflict in versioning schemes for the same packages.
The need to back up your configuration files before an update. Even the best package spec files can have mistakes. If you have modified a file which is not flagged as a configuration file, then you might lose your configuration changes. Or an update may have a different format of configuration file, requiring a manual reconfiguration. It is often best to back up your configuration files before doing updates on critical packages such as mail, web, or database server packages.
Automatic updates may not complete the entire process needed to make the system secure. For example, DNF can install a kernel update, but until the machine is rebooted (which DNF will not do automatically) the new changes won't take effect. The same may apply to restarting daemons. This can leave the user feeling that he is secure when he is not.