From owner-freebsd-current@FreeBSD.ORG  Thu Mar  4 23:00:18 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A235316A4CE
	for <freebsd-current@FreeBSD.org>;
	Thu,  4 Mar 2004 23:00:18 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EA55843D1F
	for <freebsd-current@FreeBSD.org>;
	Thu,  4 Mar 2004 23:00:16 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i257087E006207;
	Thu, 4 Mar 2004 23:00:12 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200403050700.i257087E006207@gw.catspoiler.org>
Date: Thu, 4 Mar 2004 23:00:08 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: Cy.Schubert@komquats.com
In-Reply-To: <200403050630.i256UM0f085624@cwsys.cwsent.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
Subject: Re: sysctl spinning (was: Re: ps Causes Hard Hang) (fwd)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2004 07:00:18 -0000

On  4 Mar, Cy Schubert wrote:
> So far so good, the problem appears to be fixed. I'll leave it in 
> production tonight. If I have any fallout tonight, I'll notify you tomorrow 
> morning.

I'm somewhat suprised that you haven't seen any other signs of breakage.
I'd expect to see either some sysctl calls that fail with an ENOMEM
error, or the continuation of the looping problem, depending on which
limit gets hit first.