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

starting named-chroot vs named in Centos/RHEL 7 #345

Closed
wmerkens opened this Issue Sep 14, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@wmerkens

wmerkens commented Sep 14, 2016

In the Client code for fmDNS the function getStartupScript() needs a tweak, in RHEL/Centos 7.x when using a chroot named environment you need to start named-chroot not named. I saw the you do detection of the chroot environment and according to RHEL docs the use of named-chroot is required now. I changed the line for the moment to

'CentOS' => array('/etc/init.d/named start', findProgram('systemctl') . ' start named-chroot.service'),

The fmDNS module should have a option switch asking if chroot is being used and based on it change the startup function.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Sep 16, 2016

Thanks for the report. I'll have to see how to change the service name based on whether $server_chroot_dir is set or not. The other distros will also need to be checked for this.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Sep 22, 2016

This fix is added to fmDNS v2.2.6.

@WillyXJ WillyXJ closed this Sep 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment