Submitting patches for NRPE (was: Re: NRPE and include_dir)

[Mike Chesnut]

Wanted to take one last stab at this topic from several months ago (I 
brought it up on this list last March/April).

The issue, as I see it: when you use an include_dir in your nrpe.cfg, 
the files from that directory are loaded in a nondeterministic manner. 
This means that you cannot reliably do something like have a "base" nrpe 
client config file that goes on all of your hosts, but then have a 
host-specific one that supercedes that base config file for specific 
commands.

The fix is simple, and I have a patch (against nrpe 2.12) ready that 
I've been running in production for almost a year now.  I see that there 
is now a 2.13 and I've confirmed that the patch would be the same (the 
function in question is no different in the newer version).

I've also submitted this patch to Icinga already, as they seemed 
receptive to it and I wanted to get it out for broader testing/use.

I cannot find any information about how to go about submitting a patch 
for nrpe.  The one thing I've seen is that I can open a bug on 
sourceforge, but I'm not sure where that gets me (and as I've learned, 
we don't all agree that this is a "bug" per se to begin with).  I also 
do not see any way to change the documentation (which apparently only 
exists as an .odt file) to explicitly clarify the behavior.

Can anybody point me in the right direction, please?

Thanks,
Mike

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null