From owner-freebsd-net  Wed Jun  5  0:13:12 2002
Delivered-To: freebsd-net@freebsd.org
Received: from wren.cs.unc.edu (wren.cs.unc.edu [152.2.128.86])
	by hub.freebsd.org (Postfix) with ESMTP id 451E437B400
	for <freebsd-net@FreeBSD.ORG>; Wed,  5 Jun 2002 00:13:09 -0700 (PDT)
Received: from capefear.cs.unc.edu (capefear.cs.unc.edu [152.2.128.19])
	by wren.cs.unc.edu (8.9.3/8.9.3) with ESMTP id DAA01545
	for <freebsd-net@FreeBSD.ORG>; Wed, 5 Jun 2002 03:13:08 -0400 (EDT)
Date: Wed, 5 Jun 2002 03:13:07 -0400 (EDT)
From: Nguyen-Tuong Long Le <le@cs.unc.edu>
To: freebsd-net@FreeBSD.ORG
Subject: Re: Problem with SYN cache in FreeBSD 4.5
In-Reply-To: <20020604221848.J42854-100000@patrocles.silby.com>
Message-ID: <Pine.GSO.4.10.10206050310140.18337-100000@capefear.cs.unc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org

> It appears that the primary reason a syncache abort would occur is because
> the system has run out of sockets.  Is kern.ipc.numopensockets approaching
> kern.ipc.maxsockets?

Works like a charm. Thanks! I forgot to set this when I upgraded
my system from 4.3 to 4.5 release. My bad. Thanks again!

I couldn't find the variable kern.ipc.numopensockets. Does it exist
in 4.5 or any earlier release?

Thanks again,
-- long


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message