hard-coded directives?

Support requests, bug reports, questions etc.

hard-coded directives?

Post by bo320 » Mon Sep 28, 2009 02:04

Hi there,

Are there any hard-coded directives in het nconf code?
I see for example the "passive_checks_enabled" set in the produced services.cfg, but it can't be found anywhere in the nconf configuration.
Who puts this directive in the services.cfg file?
I tried to override it by adding it as an attribute to the nconf service class, but that doesn't work.
So i am very curious why en how nconf puts this directive in the services.cfg file.

Any replies would be great!

Gr. Johan

User avatar
NConf developer
NConf developer
Posts: 725
Joined: Fri Mar 06, 2009 17:50
Location: Zurich, Switzerland

Re: hard-coded directives?

Post by agargiulo » Tue Sep 29, 2009 09:29


Yes, there are some "hardcoded features" in NConf. Some attributes are set globally for all hosts/services when the config is generated. This was done in order to simplify the configuration of a distributed environment. For most users these options are OK, although occasionally some advanced users would like more granularity.

The "passive_checks_enabled" option for instance is configured on a collector/monitor server level and is assigned globally to all items which are monitored by that server. You can change the flag by editing the collector/monitor server in NConf, but you cannot assign passive checks to one service, and active checks to another service.

This might be a feature we will implement later.

Hope this helps. Best regards,


Re: hard-coded directives?

Post by Guest » Tue Sep 29, 2009 20:34

Thanks for your reply Angelo.
Although it doesn't help me It clearifies what i already suspected...:-)
Thanks again!

Grz. Johan