From owner-freebsd-hackers Wed May 17 22:27:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 57F9237BB1D for ; Wed, 17 May 2000 22:27:05 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FUQ00EB2PT15G@falla.videotron.net> for freebsd-hackers@freebsd.org; Thu, 18 May 2000 01:27:01 -0400 (EDT) Date: Thu, 18 May 2000 01:28:28 -0400 (EDT) From: Bosko Milekic Subject: Re: leaking sockets (closure) In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Mike Silbersack Cc: freebsd-hackers@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mike, On Wed, 17 May 2000, Mike Silbersack wrote: > Heh, that's sorta neat, I guess. It'll be interesting to find out if the > leak is due to the mbuf waiting in some way, or a totally unrelated bug > we're tickling. I'd almost guess the latter. I finally peeked at the tcp_timer stuff and quickly realized: `grep keepalive /etc/defaults/rc.conf' or, equivalently, `sysctl -A | grep keepalive' should quickly make things clear... :-) Notice the explicit initialization of always_keepalive to zero in tcp_timer.c, which is what at first glance tripped me off. (I have re-simulated the exhaustion and all seems fine). -Bosko -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com bmilekic@dsuper.net * bmilekic@technokratis.com * b.milekic@marianopolis.edu "Give a man a fish and he will eat for a day. Teach him how to fish, and he will sit in a boat and drink beer all day." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message