diff options
| author | phaer <hello@phaer.org> | 2025-07-10 14:25:51 +0200 |
|---|---|---|
| committer | phaer <hello@phaer.org> | 2025-07-11 15:13:25 +0200 |
| commit | dd88db29ed76a434460fa544473eeaa867e9a6cd (patch) | |
| tree | d4ffb9234cd53b93b375cd66a0705bce21fa00fb /pkgs/development/python-modules/python-openstackclient | |
| parent | 28c73b6e0af0778aa7f016be6c0ecd3a04efb17f (diff) | |
modules/systemd-oomd: add After=systemd-sysusers.service
Before this change, systemd-oomd startup was flaky at least with
either systemd-sysusers or userborn enabled. It would restart several
times until users were provisioned, so that it finally succeeded.
An alternative would be to use a DynamicUser which was my first
approach, before I discovered that upstream added the after statement
in Dec 2024[1]. DynamicUsers could have further
implications (sandboxing, etc), so we follow upstream here.
It's not clear to me we why Upstreams "After=systemd-sysusers.service"
doesn't show up on nixos-unstable systems (systemd v257.6).
Userborn is covered, as its unit is aliased to systemd-sysusers.service.
The following test succeeded after this change on x86_64-linux:
nix-build -A nixosTests.systemd-oomd
[1]: https://github.com/systemd/systemd/commit/36dd4296806b5541eb67cd13c535eb0fe3213121
Diffstat (limited to 'pkgs/development/python-modules/python-openstackclient')
0 files changed, 0 insertions, 0 deletions