fedora-docs / release-notes

#627 F34 Change: Enable systemd-oomd by default for all variants
Closed by pbokoc. Opened by bcotton.

Closed
Reopen Issue

This issue tracks the release note for the following Fedora Change:

https://fedoraproject.org/wiki/Changes/EnableSystemdOomd

If you own this change, please add additional information here that we should communicate to Fedora users. Specifically, please consider:

  • New features available because of this change - pick 2 or 3 that are important
  • Considerations for users of previous releases of Fedora (upgrade issues, format changes, etc.)
  • Links to any upstream Release Notes
  • If this helps Fedora be a superior environment for our target audiences, please explain how so that we can emphasize this.

Your notes to us do not need to be formally written. We will edit them and add details as needed. This is a way for you to ensure that we know what is critical about your change.

If you want to write this release note, then:

  • Assign this issue to yourself
  • Check the wiki page linked above, find out what the change is about
  • Determine whether the change actually made it into the release or not[0]
  • Write a draft release note using that information against the correct branch here, in Pagure. (or see below)
  • Get in touch with the contact person/people listed on the wiki page, either through IRC or e-mail, and ask them to check your draft for technical accuracy
  • Submit your Release Note as a PR to this repository.

Once you're done with the above, make sure to either commit the relnote to an appropriate section of the Release Notes book, or, if you're not familiar with Git, AsciiDoc, or whatever else, just add it to this issue as a comment and let pbokoc[1] know that you're done with this one and you'd like the note included. Be sure to do this at least one day before the final release (October 29 according to the current schedule). Also make sure to do this even for relnotes that haven't been checked by the change owner.

[0] You can do that by asking the change owner listed on the wiki page; alternatively you can infer it by checking the tracker bug (linked in Wiki) in Bugzilla and looking at its status; see bug comments for details. Ask someone on the mailing list or on IRC if you're not sure.
[1] In #fedora-docs on FreeNode (UTC+1 timezone, online mostly during the day on weekdays), or pbokoc @redhat.com if you can't get a hold of me on IRC.

Metadata Update from @mareksu:
- Issue assigned to mareksu

Hi @dcavalca,

If you happen to have a moment before the Fedora 34 release, could you please review this last-minute systemd-oomd release note?

If you can't, don't worry about it.

Thanks!

.systemd-oomd prevents out-of-memory situations
The `systemd-oomd` service monitors swap and CGroups on your system using the Linux pressure stall information (PSI) and analyzes wasted productivity due to resource shortages. When the system is running out of memory, `systemd-oomd` terminates processes under the CGroup that exceeds the configured memory limits.
The `systemd-oomd` service is now enabled by default on new installations and when upgrading existing installations. It automatically replaces the `earlyoom` service, which previous Fedora releases used to prevent out-of-memory situations.
For information on `systemd-oomd` configuration, see the `oomd.conf` man page.

This is fine for me. I've also asked the other folks involved in the proposal to take a look. Thanks!

Fixed in #689.

Metadata Update from @pbokoc:
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.