Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nixos/dnscrypt-proxy2: service restart on failure #87145

Merged
merged 1 commit into from May 22, 2020

Conversation

snicket2100
Copy link
Contributor

@snicket2100 snicket2100 commented May 6, 2020

Motivation for this change

it does happen that dnscrypt-proxy exits when it is unable to
synchronise its resolvers metadata on startup. this can happen due
to network connectivity issues for example. not restarting it automatically
means no dns resolution will work until a manual restart is performed.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@snicket2100
Copy link
Contributor Author

snicket2100 commented May 6, 2020

I wasn't sure whether to use on-failure / on-abnormal/ on-abort instead of always. Would be happy to hear what the NixOS conventions are in this area.

@bjornfor
Copy link
Contributor

I don't know of any convention. I think the Restart= value should be decided on per service. This PR seems like a strict improvement, so I approve it.

Copy link
Contributor

@bjornfor bjornfor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: nixos commits should have nixos prefix: "nixos/dnscrypt-proxy2: ...".

it does happen that `dnscrypt-proxy` exit when it is unable to
synchronise its resolvers metadata on startup. this can happen due
to network connectivity issues for example. not restarting it automatically
means no dns resolution will work until a manual restart is performed.
@snicket2100 snicket2100 changed the title dnscrypt-proxy2: service restart on failure nixos/dnscrypt-proxy2: service restart on failure May 21, 2020
@snicket2100
Copy link
Contributor Author

Nit: nixos commits should have nixos prefix: "nixos/dnscrypt-proxy2: ...".

Fixed!

@bjornfor bjornfor merged commit 866b411 into NixOS:master May 22, 2020
@snicket2100 snicket2100 deleted the dnscrypt-proxy2-restart branch November 20, 2020 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants