diff options
| author | Léo Gaspard <leo@gaspard.io> | 2022-06-13 15:28:12 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-13 15:28:12 +0200 |
| commit | 02cd48717d5249876b181cf9555a48041dd33ae7 (patch) | |
| tree | 7019a4ee311ecaa2602549b3d626ec530029e4d0 /pkgs/games/freeciv/default.nix | |
| parent | a1ad23574310f0ca7aedd916192855a3e2a46729 (diff) | |
| download | nixpkgs-02cd48717d5249876b181cf9555a48041dd33ae7.tar nixpkgs-02cd48717d5249876b181cf9555a48041dd33ae7.tar.gz nixpkgs-02cd48717d5249876b181cf9555a48041dd33ae7.tar.bz2 nixpkgs-02cd48717d5249876b181cf9555a48041dd33ae7.tar.lz nixpkgs-02cd48717d5249876b181cf9555a48041dd33ae7.tar.xz nixpkgs-02cd48717d5249876b181cf9555a48041dd33ae7.tar.zst nixpkgs-02cd48717d5249876b181cf9555a48041dd33ae7.zip | |
nixos/openldap: fix systemd rejecting notification (#177084)
On one of the two machines I have running openldap, openldap failed to start due to a "timeout". Increasing the allowed startup delay didn't help. I noticed the following in logs: ``` openldap.service: Got notification message from PID 5224, but reception only permitted for main PID 5223 ``` It turns out that on this machine at least, openldap apparently sends the notification from a non-main process, which means that we need this NotifyAccess setting for systemd to record that it successfully started. Without it, after 30 seconds systemd kills the process because it didn't receive the sd_notify call. Somehow the other machine I have on nixos running ldap works fine even without this, but I could not figure out what changes the behavior. Given that AFAIU NotifyAccess still restricts to "from the cgroup of the service", I think this change should be safe.
Diffstat (limited to 'pkgs/games/freeciv/default.nix')
0 files changed, 0 insertions, 0 deletions