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

rdnssd: fix service #38944

Closed
wants to merge 1 commit into from
Closed

rdnssd: fix service #38944

wants to merge 1 commit into from

Conversation

woffs
Copy link
Contributor

@woffs woffs commented Apr 14, 2018

rdnssd did not start properly in 18.03:

Starting RDNSS daemon...
rdnssd.service: Permission denied while opening PID file or unsafe symlink chain: /run/rdnssd/rdnssd.pid
rdnssd.service: Start operation timed out. Terminating.
rdnssd.service: Failed with result 'timeout'.
Failed to start RDNSS daemon.

Leaving /run/rdnssd owned by root and moving resolv.conf into a separate
subdir owned by rdnssd fixes this.

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • 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 nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

rdnssd did not start properly in 18.03:

  Starting RDNSS daemon...
  rdnssd.service: Permission denied while opening PID file or unsafe symlink chain: /run/rdnssd/rdnssd.pid
  rdnssd.service: Start operation timed out. Terminating.
  rdnssd.service: Failed with result 'timeout'.
  Failed to start RDNSS daemon.

Leaving /run/rdnssd owned by root and moving resolv.conf into a separate
subdir owned by rdnssd fixes this.
@xeji
Copy link
Contributor

xeji commented Aug 28, 2018

Thank you for your contribution, and sorry that it took so long for someone to look at it.
I could not reproduce the issue on current master (94a906b).
The service starts up without errors. Closing since this change is no longer required.

@xeji xeji closed this Aug 28, 2018
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

3 participants