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

chroot option + systemd do not coexist well #4848

Closed
zeha opened this issue Jan 3, 2017 · 1 comment

Comments

@zeha
Copy link
Collaborator

commented Jan 3, 2017

There are various issues when running pdns with chroot= set under systemd.

IIRC:

  • notification to systemd fails because the systemd socket is unreachable
  • pdns_control has (with some specific settings) trouble talking to the daemon

Personally, I'd think refusing to start under systemd with chroot set would be good.

@pieterlexis

This comment has been minimized.

Copy link
Member

commented Jan 3, 2017

note:

Should be easy to detect, systemd creates the NOTIFY_SOCKET environment variable, we can refuse to start if it is present and chroot= is in the config

pieterlexis added a commit to pieterlexis/pdns that referenced this issue Jan 16, 2017

pieterlexis added a commit to pieterlexis/pdns that referenced this issue Jan 16, 2017

pieterlexis added a commit to pieterlexis/pdns that referenced this issue Feb 14, 2017

pieterlexis added a commit to pieterlexis/pdns that referenced this issue May 9, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.