-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
$conf_d and $unbound_conf_d are not documented and unclear how they differ beyond their location #342
Comments
I'm not sure, but a possible explaination was: |
Looking through the history i think theses parameters probably point to the same thing but are perhaps different on different distros. The commit that introduced the conf_d directory mentions SuSE support. and the PR (#225) that added |
AFAICT the intention of theses two parameters is the same so lets merge them fixes voxpupuli#342
AFAICT the intention of theses two parameters is the same so lets merge them fixes voxpupuli#342
AFAICT the intention of theses two parameters is the same so lets merge them fixes voxpupuli#342
AFAICT the intention of theses two parameters is the same so lets merge them fixes voxpupuli#342
AFAICT the intention of theses two parameters is the same so lets merge them fixes voxpupuli#342
AFAICT the intention of theses two parameters is the same so lets merge them fixes voxpupuli#342
AFAICT the intention of theses two parameters is the same so lets merge them fixes voxpupuli#342
AFAICT the intention of theses two parameters is the same so lets merge them fixes voxpupuli#342
I'm trying to understand the difference between the undocumented
$conf_d
and$unbound_conf_d
parameters of theunbound
class. Neither seems to be used anywhere outside of ensuring directory ownership (but not included in the configuration by default), and in the case of the$unbound_conf_d
directory, you can also ensure the directory is purged of unmanaged configurations.Can we get these parameters documented based on the intended usage?
The text was updated successfully, but these errors were encountered: