From owner-freebsd-ports@FreeBSD.ORG Mon Feb 28 12:42:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 414E1106566B; Mon, 28 Feb 2011 12:42:38 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id DB8578FC0C; Mon, 28 Feb 2011 12:42:37 +0000 (UTC) Received: by qwj8 with SMTP id 8so2993622qwj.13 for ; Mon, 28 Feb 2011 04:42:37 -0800 (PST) Received: by 10.229.95.11 with SMTP id b11mr4093778qcn.28.1298896956796; Mon, 28 Feb 2011 04:42:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.250.66 with HTTP; Mon, 28 Feb 2011 04:42:15 -0800 (PST) In-Reply-To: <86lj1ah2ce.fsf@chateau.d.if> References: <86bp2d1wit.fsf@chateau.d.if> <86oc6dzf1z.fsf@chateau.d.if> <86lj1ah2ce.fsf@chateau.d.if> From: =?UTF-8?Q?Marius_N=C3=BCnnerich?= Date: Mon, 28 Feb 2011 13:42:15 +0100 Message-ID: To: Ashish SHUKLA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: pdnsd leaking udp sockets X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2011 12:42:38 -0000 On Sun, Feb 20, 2011 at 21:34, Ashish SHUKLA wrote: > Hi Marius, > > Marius N=C3=BCnnerich writes: > > [...] > >> Ok, I applied the patch and reinstalled the port. I will leave it >> running for a few days and report back. So far it's looking good. >> Thank you very much! :) > OK, I had it running for a while now with your fix. It's not leaking anymor= e. There is still one close() missing before a return in that same function. > I talked to Paul (the upstream author of pdnsd), and he suggested running > dns/pdnsd with following command-line (requires devel/valgrind port): > > % valgrind --tool=3Dmemcheck --leak-check=3Dyes --track-fds=3D=3Dyes pdns= d --nodaemon I'll try this too if I can find the time, but so far it doesn't seem to leak memory.