Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2016-01-22 Thread Alexander Wirt
On Fri, 22 Jan 2016, Fabien COELHO wrote: > > Hello Alexander, > > > ISTM that you did not answer about my point that the current configuration > file is misleading, as the 'dont_blame_nrpe' option is ignored but there is > no warning about that fact in the file nor in the log. If it had been t

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2016-01-22 Thread Fabien COELHO
Hello Alexander, ISTM that you did not answer about my point that the current configuration file is misleading, as the 'dont_blame_nrpe' option is ignored but there is no warning about that fact in the file nor in the log. If it had been the case, I would have lost much less time. The "ju

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2016-01-22 Thread Fabien COELHO
Sigh. I've lost 1 hour on this "improvement". Please note that there is still a bug: the installed "/etc/nagios/nrpe.cfg" configuration file now contains a option which is ignored, but AFAICS there is no warning about that fact in the file nor in the log when starting nrpe, so people will kee

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2016-01-22 Thread Alexander Wirt
On Fri, 22 Jan 2016, Fabien COELHO wrote: > > Sigh. I've lost 1 hour on this "improvement". > > Please note that there is still a bug: the installed "/etc/nagios/nrpe.cfg" > configuration file now contains a option which is ignored, but AFAICS there > is no warning about that fact in the file no

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2015-09-01 Thread Alexander Wirt
On Tue, 01 Sep 2015, David Rosenstrauch wrote: > On 09/01/2015 11:15 AM, Alexander Wirt wrote: > >On Tue, 01 Sep 2015, David Rosenstrauch wrote: > > > >>On 09/01/2015 10:58 AM, Alexander Wirt wrote: > >>>On Tue, 01 Sep 2015, David Rosenstrauch wrote: > >>> > So what is the recommended workarou

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2015-09-01 Thread David Rosenstrauch
On 09/01/2015 11:15 AM, Alexander Wirt wrote: On Tue, 01 Sep 2015, David Rosenstrauch wrote: On 09/01/2015 10:58 AM, Alexander Wirt wrote: On Tue, 01 Sep 2015, David Rosenstrauch wrote: So what is the recommended workaround for users who are currently relying on this functionality? either g

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2015-09-01 Thread Alexander Wirt
On Tue, 01 Sep 2015, David Rosenstrauch wrote: > On 09/01/2015 10:58 AM, Alexander Wirt wrote: > >On Tue, 01 Sep 2015, David Rosenstrauch wrote: > > > >>So what is the recommended workaround for users who are currently relying on > >>this functionality? > >either get your environment fixed, or bui

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2015-09-01 Thread David Rosenstrauch
On 09/01/2015 10:58 AM, Alexander Wirt wrote: On Tue, 01 Sep 2015, David Rosenstrauch wrote: So what is the recommended workaround for users who are currently relying on this functionality? either get your environment fixed, or build your own package. Alex Not sure what you mean by "get you

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

2015-09-01 Thread Alexander Wirt
On Tue, 01 Sep 2015, David Rosenstrauch wrote: > So what is the recommended workaround for users who are currently relying on > this functionality? either get your environment fixed, or build your own package. Alex