nixos/doc/rl-2505: Fix wording of users.users subuid allocation note

Co-authored-by: Leona Maroni <dev@leona.is>
This commit is contained in:
ash
2025-05-17 16:19:46 +01:00
co-authored by Leona Maroni
parent 5db992b91d
commit 75097de8fb
@@ -274,7 +274,7 @@
to review the new defaults and description of
[](#opt-services.nextcloud.poolSettings).
- In `users.users` allocation on systems with multiple users it could happen that collided with others. Now these users get new subuid ranges assigned. When this happens, a warning is issued on the first activation. If the subuids were used (e.g. with rootless container managers like podman), please change the ownership of affected files accordingly.
- In `users.users` subuid allocation on systems with multiple users it could happen that some users' allocated subuid ranges collided with others. Now these users get new subuid ranges assigned. When this happens, a warning is issued on the first activation. If the subuids were used (e.g. with rootless container managers like podman), please change the ownership of affected files accordingly.
- The `services.locate` module does no longer support findutil's `locate` due to its inferior performance compared to `mlocate` and `plocate`. The new default is `plocate`.
As the `service.locate.localuser` option only applied when using findutil's `locate`, it has also been removed.