In nrpe.c, readdir() is used to load files from the config directory (include_dir), which is totally non-deterministic in the order the files are read. It'd be much nicer if the order of loading was well-defined.
This would allow, e.g., for being able to override a command in a "base" file (e.g., 000-nrpe.cfg) with a more host-specific file (e.g., 200-myhost.cfg). We can essentially consider this to be a scalability enhancement for NRPE.
Currently the order is neither defined nor documented, so there should be no installations that are reliant on files from an include_dir being loaded in a particular order. (Or if they are, it's by accident. This could lead to an unpleasant surprise after upgrading to a version with this new feature implemented.)
This is the same as this Icinga issue: https://dev.icinga.org/issues/2318