@orlitzky i understand the problem you had, in my distro it can be fixed with marking procps 3.3.10 to conflict with monitoring-plugins < 2.1.1-2, where monitoring-plugins == 2.1.1-2 is the "new" version that uses paths from 3.3.10, so users are forced to upgrade both or neither.
as for looking up programs from `PATH` security concern, there already exists `--with-trusted-path=PATH` configure option, so it should be "secure" to search them from there runtime. and i think it would also simplify whole `configure.ac` and probably cruft needed to add support for new program for use of plugin. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/issues/1394#issuecomment-187091979
