NSClient++ Help (#1) - Includes on v0.4.0? (#970) - Message List

Includes on v0.4.0?

I've been using NSClient++ for years now and one of the features that I found utilising since v0.3.1 was includes. This allowed me to have a single nsc.ini file that was used across the hundreds of servers I monitor where the only thing that I would change are the files to include on each server - and these additional .ini files contained host-specific external scripts.

I've recently started trying to upgrade one of the server that I monitor to v0.4.0. When attempting an upgrade, the installer could not convert my ini file due to the presence of "includes" statements. So I carried on and thought that I'd go the the config by hand (which I was expecting to do anyway). However, I don't see any way to include other files in the configuration from looking at the documentation.

Taking an example, I had the following config section in my ini file on one of my HP ProLiant? DL360g5 Windows 2003 servers, which acts as a transcoder: 

[includes]
includes\dl360g5.ini
includes\transcode.ini
includes\windows2k3.ini

... and dl360g5.ini, transcode.ini and windows2k3.ini contained External Script definitions relevant for all of my dl360g5, transcode and Windows 2003 servers respectively.

Can I do the same configuration under 0.4.0, or must all definitions be listed in the main NSClient.ini file?

Spingo
05/11/12 07:25:08 (13 months ago)
Tree View Flat View (newer first) Flat View (older first)
  • Message #2608

    Yes you can still use includes.

    Conversion will convert all keys to one big file. But manually you can convert (and/or split) it.

    Includes work better actually in 0.4.0. as you can in clude both old, ini, registry and http so you can mix and match.

    For instance:

    includes/new.ini 

    [/settings/external scripts/alias]
new_foo=bar

    includes/old.ini 

    [External Alias]
old_foo=bar

    nsclient.ini 

    [/modules]
CheckExternalScripts = 1
[/includes]
test1=old://includes/old.ini
test2=ini://includes/new.ini

    A difference as you might have noticed is that you need to enter a "key" this is not really used currently so it can be anything as long as it is unique.

    mickem
    05/19/12 11:11:44 (12 months ago)
    • Message #2609

      Just as a side note:

      So an excellent way to handle migrations is to use includes like so: nsclient.ini 

      ...
[/includes]
legacy=old://nsc.ini

      Michael Medin

      mickem
      05/19/12 11:12:43 (12 months ago)
Tree View Flat View (newer first) Flat View (older first)

Subscriptions