RPM-OSTREED-AUTOMA(8)

πŸ’– RPM-OSTREED-AUTOMATIC πŸ’–

okay bestie, sit down, we're talking about the automatic update girlies πŸ’…

✨ NAME ✨

rpm-ostreed-automatic.service, rpm-ostreed-automatic.timer β€” they run the automatic updates policy. that's it, that's the whole job, and they do it flawlessly 🫢


🌸 SYNOPSIS 🌸

rpm-ostreed-automatic.service

rpm-ostreed-automatic.timer

no args, no flags, no drama. two units, just vibing ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

so the service unit is the one that actually enacts the AutomaticUpdatePolicy setting that lives in rpm-ostreed.conf(5). like, it reads the policy and then does the thing. for example β€” and this is the example, not me making stuff up β€” if the current policy is "check", then the service will check for updates. simple as that. iconic behaviour honestly πŸ’–

meanwhile the timer unit is the one deciding how often the service unit gets run. it's the schedule girlie. the vibe-setter. the "when are we doing this" of it all.

⚠️ important, no cap: disabling or masking this timer unit effectively disables automatic updates, no matter what the setting in rpm-ostreed.conf(5) says. the config can scream, the timer's not listening. so don't be out here editing config files wondering why nothing's updating πŸ’€

if you wanna know how to actually control systemd timers (start, stop, schedule, all of it), go read systemd.timer(5). it's giving documentation. it's giving answers. πŸ“šβœ¨


πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page bestie, we ate and left no crumbs πŸŽ€

this was brought to you by the rpm-ostree crew, page RPM-OSTREED-AUTOMA(8) β€” go forth and let your timers run on schedule, mwah πŸ’œβœ¨

πŸ“¦ where this page comes from