DNF5-AUTOMATIC(8)

πŸ’… DNF5-AUTOMATIC(8) β€” the dnf5 manual, automatic edition πŸŽ€

okay bestie, so the header says DNF5-AUTOMATIC(8) and it lives in the dnf5 manual, and literally the whole vibe of this page is "let the computer handle its own upgrades while you go touch grass." let's get into it ✨


🌸 NAME 🌸

dnf5-automatic β€” the Automatic Command. that's it, that's the name πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

dnf5 automatic [options]

✨ DESCRIPTION ✨

so this is basically an alternative CLI to dnf upgrade, except it's built with special facilities to make it suitable to be run automatically and regularly from systemd timers, cron jobs and similar. main character energy for a package manager ngl πŸ‘‘

The operation of the tool is controlled by configuration files. Default values are set from the /usr/share/dnf5/dnf5-plugins/automatic.conf config file, and then host-specific overrides from /etc/dnf/automatic.conf are applied on top. so like, defaults first, your spicy takes second 🫢

The tool synchronizes package metadata as needed, then checks for updates available for the given system, and then either exits, downloads the packages, or downloads and applies the updates. The outcome of the operation is then reported by a selected mechanism β€” for instance via the standard output, email, or MOTD messages πŸ“¬

The systemd timer unit dnf5-automatic.timer will behave as the configuration file specifies (see below) with regard to whether to download and apply updates. iykyk πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • --timer β€” apply a random delay before execution. lil bit of chaos, lil bit of jitter ⏰

The following options can be used to override values from the configuration file (yes, you can boss it around):

  • --downloadupdates β€” automatically download updated packages.
  • --no-downloadupdates β€” do not automatically download updated packages.
  • --installupdates β€” automatically install downloaded updates. heads up: this implies --downloadupdates πŸ‘€
  • --no-installupdates β€” do not automatically install downloaded updates.

πŸ”₯ RUN DNF5 AUTOMATIC SERVICE πŸ”₯

The service is typically executed using the systemd timer dnf5-automatic.timer. To configure the service, customize the /etc/dnf/automatic.conf file. You can either copy the distribution config file from /usr/share/dnf5/dnf5-plugins/automatic.conf and use it as a baseline, or create your own configuration file from scratch with only the required overrides. both are valid, do whatever slays πŸ’…

Then enable the timer unit:

systemctl enable --now dnf5-automatic.timer

and that's it, she's on a schedule now 🌈


🧚 CONFIGURATION FILE FORMAT 🧚

The configuration file is separated into topical sections. very organized, very demure ✨

🌸 [commands] section 🌸

Setting the mode of operation of the program. the control room, basically πŸŽ›οΈ

  • apply_updates β€” boolean, default: False Whether packages comprising the available updates should be applied by dnf5-automatic.timer, i.e. installed via RPM. Implies download_updates. Note that if this is set to False, downloaded packages will be left in the cache till the next successful DNF transaction. (yes, they just vibe in the cache 🫠)
  • download_updates β€” boolean, default: True Whether packages comprising the available updates should be downloaded by dnf5-automatic.timer.
  • network_online_timeout β€” time in seconds, default: 60 Maximal time dnf5 automatic will wait until the system is online. 0 means that network availability detection will be skipped. zero = no waiting, we go πŸ’¨
  • random_sleep β€” time in seconds, default: 0 Maximal random delay before downloading (only applied if --timer option was used). Note that, by default, the systemd timers also apply a random delay of up to 1 hour. so yeah, double delay potential, iconic ⏳
  • upgrade_type β€” either one of default, security, distro-sync, default: default What kind of upgrades to look at. default signals looking for all available updates, security only those with an issued security advisory, distro-sync synchronizes packages to the latest available versions in the enabled repositories (similar to dnf5 distro-sync).
  • reboot β€” either one of never, when-changed, when-needed, default: never When the system should reboot following upgrades. never does not reboot the system. when-changed triggers a reboot after any upgrade. when-needed triggers a reboot only when rebooting is necessary to apply changes, such as when systemd or the kernel is upgraded. choose your fighter πŸ₯Š
  • reboot_command β€” string, default: shutdown -r +5 'Rebooting after applying package updates' Specify the command to run to trigger a reboot of the system. For example, to skip the 5-minute delay and wall message, use shutdown -r. (rude but efficient lmao)

πŸ’Œ [emitters] section πŸ’Œ

Choosing how the results should be reported. how do we spill the tea, basically β˜•

  • emit_via β€” list, default: stdio List of emitters to report the results through. Available emitters are stdio to print the result to standard output, command to send the result to a custom command, command_email to send an email using a command, email to send the report via email using SMTP server (see [email] section for requirements), and motd sends the result to /etc/motd.d/dnf5-automatic file. pick your fave, or several πŸ’–
  • system_name β€” string, default: hostname of the given system How the system is called in the reports. her government name πŸͺͺ
  • emit_no_updates β€” boolean, default: False Whether to emit a message when nothing interesting happened β€” the operation succeeded and no packages were available/installed. honestly sometimes silence is the moment 🀫

🐚 [command] section 🐚

The command emitter configuration. Variables usable in format string arguments are body with the message body.

  • command_format β€” format string, default: cat The shell command to execute.
  • stdin_format β€” format string, default: {body} The data to pass to the command on stdin.

πŸ“§ [command_email] section πŸ“§

The command email emitter configuration. Variables usable in format string arguments are body with message body, subject with email subject, email_from with the "From:" address and email_to with a space-separated list of recipients.

  • command_format β€” format string, default: mail -Ssendwait -s {subject} -r {email_from} {email_to} The shell command to execute.
  • email_from β€” string, default: root Message's "From:" address.
  • email_to β€” list, default: root List of recipients of the message.
  • stdin_format β€” format string, default: {body} The data to pass to the command on stdin.

πŸ’œ [email] section πŸ’œ

The email emitter configuration. This emitter sends messages directly via an SMTP server using libcurl. It requires libcurl with SMTP protocol support. Some distributions ship a minimal variant of libcurl without SMTP support. On Fedora, this can be resolved by running dnf5 swap libcurl-minimal libcurl. Alternatively, use the command_email emitter which does not require SMTP support in libcurl. Credentials for the SMTP server are read from the ~/.netrc file. πŸ”

ngl the "minimal libcurl has no SMTP" thing is a real gotcha, so like, check before you flame the config πŸ”₯
  • email_from β€” string, default: root Message's "From:" address.
  • email_to β€” list, default: root List of recipients of the message.
  • email_host β€” string, default: localhost Hostname of the SMTP server used to send the message.
  • email_port β€” integer, default: 25 Port number to connect to at the SMTP server.
  • email_tls β€” either one of no, yes, starttls, default: no Whether to use TLS, STARTTLS or no encryption to connect to the SMTP server.

🌈 [base] section 🌈

Can be used to override settings from DNF's main configuration file. See dnf5.conf(5). yes bestie, that's a SEE ALSO, go read it πŸ’…


πŸ‘‘ Author πŸ‘‘

See AUTHORS.md in dnf5 source distribution. (the whole squad 🫢)


Contributors to the dnf5 project.


alright that's the whole page, no cap πŸ™ˆ β€” this is dnf5-automatic(8) from the dnf5 manual, dated Oct 17, 2026, and that's the tea bestie, go let your timers do their thing πŸ’–πŸŽ€πŸ¦‹βœ¨

πŸ“¦ where this page comes from