NRPE, Debian and RedHat inconsistencies and question about repositories.

Hi ​@benoitp,

• Sury: you can ignore it. I only mentioned it because I met this issue while testing the procedure on a minimal Debian image (hence “At this point, if you get this error […] You may solve it by running [...]”). If you think it’s misleading, then we probably should remove it.
• Config file paths: I’m not a Linux packagin expert, but I suspect there would be a conflict if the official NRPE package and ours shared common files or directories, that could lead to uncertain behaviour if anyone installs both on the same server. Same for the user.
• Why two different package? Why do we tell to install Nagios’ official NRPE package on RH-like distros whereas we package our own flavour on Debian? Because on the latter, the official package is more hardened than on RH, since it’s compiled in a way that forbids to pass command arguments to the commands (ie they hard-disable the dont_blame_nrpe option). Since the whole point of our templates is to be able to configure the thresholds in the WUI, we had to adapt to this situation buy making our own build (actually the whole story is a bit more complicated than that, but it’s not relevant when talking about NRPE v4).

Now that it seems that NRPE is not the future of monitoring, and that we provide our own agent, we don’t plan on aligning both distros families.