English Spanish
Best practices when using automatic updates
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.
Auter is not scheduled by default. Add a schedule for `--prep` (if you want to pre-download updates) and `--apply` (install updates). The installed cron job which you can see in `/etc/cron.d/auter` contains lots of examples.
auter --disable
auter --apply
As of Fedora 26 there are now three timers that control dnf-automatic.
As an alternative to dnf-automatic, https://github.com/rackerlabs/auter[auter] can be used. This operates in a similar way to dnf-automatic, but provides more flexibility in scheduling, and some additional options including running custom scripts before or after updates, and automatic reboots. This comes at the expense of more complexity to configure.
Another common problem is having automatic updates run when it isn't desired (holidays, weekends, vacations, etc). If there are times that no one will be around to fix any problem arising from the updates, it may be best to avoid doing updates on those days.
Alternatives to automatic updates
Alternative methods