Am 29.05.2013 15:53, schrieb Robin Sonefors:
> On 2013-05-27 10:46, Jonas Meurer wrote:
>> Hello,
>>
>> while switching from external perl interpreter to ePN, we stumbled over
>> the empty arguments bug in ePN
>> (http://tracker.nagios.org/view.php?id=88). This bug keeps us from
>> using
>> ePN for a lot of the check commands we use.
>>
>> Now I wonder: why is the bugreport closed? In my opinion the bug is not
>> fixed at all. As suggested in comment 2, patching p1.pl to ignore empty
>> arguments would be the proper fix, right?
>
> It's closed, because epn is gone from nagios 4.
Thanks for clarifying. Will nagios 4 be released in near future? So far
most people still use nagios 3. I don't think that it's a good practice
to close valid bugreports for supported major releases. Instead they
should be restricted to the major release in question. Or at least a
comment describing the reason for closing would be much appreciated
Thanks a lot for the work on nagios.
Kind regards,
jonas
> In nagios 3, the only way to get good performance for something like
> perl was to build something like epn. Unfortunately, the way epn worked,
> bugs in the epn implementation caused nagios to leak memory or even
> crash, which is exactly what you don't want from the system you install
> in order to, among other things, discover memory leaks or crashes.
>
> The nagios 4 alternative is to build specialized worker daemons. Doing
> that should improve performance as much as epn - if not more - without
> any risk for bugs to wreak havoc for anything but their own check(s). An
> epn-style perl worker could be built, but hasn't yet.
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: jonas@freesources.org