On Mon, 2020-12-21 at 12:44 -0600, Michael Catanzaro wrote: > On Mon, Dec 21, 2020 at 9:59 am, Davide Cavalca via devel > <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > We had thought about that, but one concern was migrating custom > > configuration that one might have for earlyoom, which could be > > tricky. > > If we're ok with unconditionally migrating to oomd with its default > > config, that should be pretty straightforward to do. > > Yup, that's fine. It's expected that custom configuration goes away > during a major architectural change like this. > In that case we should document how to preserve earlyoom in the F34 release notes, similar to how we have documentation on how to opt out of systemd-resolved: have a systemd preset that explicitly enables earlyoom and disables oomd. And update the Change Proposal to include modifying the default presets? -- Michel Alexandre Salim profile: https://keyoxide.org/michel@xxxxxxxxxxxxxxx chat via email: https://delta.chat/ GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
