> -----Original Message-----
> From: Andreas Ericsson [mailto:a...@op5.se]
> Sent: Wednesday, May 09, 2012 3:53 PM
> To: Nagios Users List
> Cc: Frost, Mark {BIS}
> Subject: Re: [Nagios-users] Any upcoming release?
> On 05/09/2012 07:45 PM, Frost, Mark {BIS} wrote:
>> 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.erics...@op5.se
Aha! Thanks. Yeah, I was little struck by how this seemed more like a 3.3.2
release than a release that indicated something significant going on under
the covers.
I guess there's now the problem of when the i/o broker is ready, is that
a 3.4.1 release? Seems kind of major for that.
Mark
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
