Extra-Opts configuration file location(s)

William Leibzon william at leibzon.org
Wed Jun 18 15:56:21 CEST 2014

Different distributions have different criteria for set of paths and
extensions for config files.

But I'd go with:

Because distributions typically don't mind packages having their own
subdirectory in /etc. And some prefer that and create one even if
original package would just put config file in /etc.

And the most popular extension in unix world for config files is .conf
after that its .cfg and .ini is least popular. You can check your own
distributions to see if its something like that. But since we already
went with .ini that is fine as far as I'm concerned.

On Wed, Jun 18, 2014 at 3:15 AM, Holger Weiß <holger at zedat.fu-berlin.de> wrote:
> * Holger Weiß <holger at zedat.fu-berlin.de> [2014-06-18 10:51]:
>> In the upcoming Monitoring Plugins release, the Extra-Opts feature will
>> be enabled by default.  See:
>>       https://www.monitoring-plugins.org/doc/extra-opts.html
>> The configuration file used by that feature can be specified on the
>> command line or via an environment variable.  If neither is done, a list
>> of default locations is searched.
> And what about these default locations?  Is everyone fine with the
> following two path names?
> - /usr/local/etc/monitoring-plugins.ini
> - /etc/monitoring-plugins.ini
> Or shall we also support subdirectories?  E.g.:
> - /usr/local/etc/monitoring-plugins/monitoring-plugins.ini
> - /etc/monitoring-plugins/monitoring-plugins.ini
> Or would be prefer a different file extension (such as ".cfg" or
> ".conf")?
> Holger

More information about the Devel mailing list