-
Notifications
You must be signed in to change notification settings - Fork 63
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
add support for configurable relative configuration paths #491
Conversation
as introduced in - naemon/naemon-core#491
2134722
to
8534855
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also please add an example directive for config_rel_path
into the naemon.cfg
8534855
to
e01a2db
Compare
Sure, i updated the example naemon.cfg and also added a description. |
Naemon already supports relative include paths and uses the folder of the main naemon.cfg as base path. This is fine unless you want to generate the main naemon.cfg and start naemon from a tmp folder. In this case, i'd like to set the base path from the config file. By default nothing changes, but you can now override this by setting `config_rel_path`. Signed-off-by: Sven Nierlein <sven@consol.de>
e01a2db
to
01db9e9
Compare
…) docs Relates to: naemon/naemon-core#491 Signed-off-by: nook24 <info@nook24.eu>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perfect, thanks |
as introduced in - naemon/naemon-core#491
Naemon already supports relative include paths and uses the folder of the main naemon.cfg as base path.
This is fine unless you want to generate the main naemon.cfg and start naemon from a tmp folder. In this case, i'd like to set the base path from the config file.
By default nothing changes, but you can now override this by setting
config_rel_path
.