Bleh. It's too late and to sit up and rebase 160-odd patches on top of
20 to fix a single broken one.
For those using the 3.4.0 release, I've cherry-picked all patches that
went in the 3.4.0-release apart from the broken execvp patch and added
them on top of the worker-process code.
If anyone's interested in trying them out, you can get them from
git://github.com/ageric/nagios.git or possibly get a snapshot somewhere
at https://github.com/ageric/nagios
Consider it 3.5.0-alpha or something. It still needs a lot of testing,
but it's been ticking along quite nicely in our lab the past 4 months,
running checks and generally just working with livestatus and Merlin
enabled.
Granted, that part of our lab doesn't use passive check results, but
most of the rest is tested and known to work pretty well, apart from
the small memory leak mentioned below (but who knows? Someone might
even fix that now that it's in the open).
Happy testing.
I'll get a proper fix in for the double-quote issue on friday, as I've
got presentations to run all day tomorrow.
On 05/09/2012 09:53 PM, Andreas Ericsson wrote:
> On 05/09/2012 07:45 PM, Frost, Mark {BIS} wrote:
>>
>>> -----Original Message-----
>>> From: Andreas Ericsson [mailto:ae@op5.se]
>>> Sent: Thursday, April 05, 2012 4:34 AM
>>> To: Nagios Users List
>>> Subject: Re: [Nagios-users] Any upcoming release?
>>
>>> On 04/05/2012 07:31 AM, Yu Watanabe wrote:
>>>> Hi all!
>>>>
>>>> I would like to know if there are any plans for the nagios v 3.4.x.
>>>> It has been a while since the last release so I was very curious about it.
>>
>>
>>> There is. Nagios 3.4 will be a single-threaded and event-driven application
>>> that sports an I/O-broker and vastly improved check performance. In essence,
>>> we've removed 2 fork() calls, 4 disk searches, 2 filewrites and 2 filereads
>>> from each check being performed. There's also a fixed usage of the current
>>> scheduling queue implementation which turns scheduling new checks from its
>>> current O(n) behaviour to O(1). This will provide a huge benefit for large
>>> installations, and combined with the worker process code we're currently
>>> seeing a 12-fold increase in the amount of checks Nagios can execute, but
>>> it's still too early to tell what other things are affected. The external
>>> command pipe might be a bottleneck if one uses large amounts of passive
>>> checks, for example.
>>
>>> It's currently in late alpha, so beta releases should be available in a
>>> month or so.
>>
>>> --
>>> Andreas Ericsson andreas.ericsson@op5.se
>>
>> Andreas,
>>
>> I'm a little confused about this. I've been eagerly awaiting these
>> gee-wiz-bang space-age changes, but when I looked over the change list
>> for 3.4.0 that Ethan sent they seem like mostly minor changes. Or
>> perhaps they just don't describe things in enough detail to match up the
>> rather significant architectural changes listed above.
>>
>> Is this the super-summarized bullet item that refers to the change above?
>>
>> ENHANCEMENTS
>> * Use execv() to execute active check commands (#86 - Ton Voon, dnsmichi)
>>
>
> Nopes, it's not, and that patch is actually broken. My code still leaks (about
> 1MB per 24 hours with 1000 checks / second), so I've held it back a bit. I
> didn't know they were going to hit the release button so fast, and without a
> beta period.
>
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: ae@op5.se