--=-4n3syzUKCajBd9AKRtJD
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Forwarding this on in case anyone else has seen this behaviour and has
some suggestions. I'll give it a run through valgrind and see if I can
spot anything this evening.
--=-4n3syzUKCajBd9AKRtJD
Content-Disposition: inline
Content-Description: Forwarded message - Memory leak in Nagios head
Content-Type: message/rfc822
Return-Path:
Delivered-To: [email protected]
Received: from smtp-gw1.op5.se (linux-server1.op5.se [193.201.96.2]) by
zero.voxel.net (Postfix) with ESMTP id 19DF024AE03 for
; Mon, 29 Nov 2004 06:47:30 -0500 (EST)
Received: from [192.168.1.20] (1-2-9-7b.gkp.gbg.bostream.se
[82.182.116.45]) by smtp-gw1.op5.se (Postfix) with ESMTP id D72666BD0F;
Mon, 29 Nov 2004 12:47:27 +0100 (CET)
Message-ID:
Date: Mon, 29 Nov 2004 12:47:27 +0100
From: Andreas Ericsson
User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [email protected]
Cc: [email protected]
Subject: Memory leak in Nagios head
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Ahoy Ethan.
There's a memory leak in Nagios HEAD, causing it to crash when (it
seems) enough checks has been executed. I would have emailed the
nagios-devel list but I believe I'm still banned from it pending a
solution to the sourceforge list server fuckup? Could one of you forward
this to that list, please?
It's compiled without embedded perl, and without perl caching, like so;
./configure --prefix=/opt/monitor
I'll start digging today, so I might have a patch ready for you soon.
I Cc'ed Matthew Kent on this as well, seeing as he's been very helpful
with the finding and fixing earlier.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Lead Developer
--=-4n3syzUKCajBd9AKRtJD--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]