From owner-freebsd-current Thu Dec 12 5:10: 5 2002 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 86B6B37B401; Thu, 12 Dec 2002 05:10:04 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65B9E43EC2; Thu, 12 Dec 2002 05:10:00 -0800 (PST) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Thu, 12 Dec 2002 08:09:59 -0500 Message-ID: From: Don Bowman To: 'Sean Chittenden' , current@FreeBSD.org Subject: RE: sysctl -a loops forever... Date: Thu, 12 Dec 2002 08:09:49 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: Sean Chittenden [mailto:seanc@FreeBSD.org] > > Anyone seen sysctl -a loop forever? I haven't been able to track down > the MIB that it's gettinng hung up on, but it looks like there's a > flaw in the algo that is walking through the MIBs. Given that this > halts the machine while trying to collect entropy (sysctl -a is used > to help feed /dev/random) at system start up, I think it's something > worth addressing or pointing out. -sc I've observed this when e.g. I had too many nmbclusters configured, ie when vm.kvm_free was too low (0 in my case :) --don (don@sandvine.com www.sandvine.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message