From owner-freebsd-current@FreeBSD.ORG Sun Sep 14 19:13:10 2003 Return-Path: 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 E3FE516A4C0 for ; Sun, 14 Sep 2003 19:13:10 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 145E843FAF for ; Sun, 14 Sep 2003 19:13:10 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 0619E72DA3; Sun, 14 Sep 2003 19:13:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 011D072DA2; Sun, 14 Sep 2003 19:13:09 -0700 (PDT) Date: Sun, 14 Sep 2003 19:13:09 -0700 (PDT) From: Doug White To: masta In-Reply-To: <33165.12.238.113.137.1063565187.squirrel@mail.yazzy.org> Message-ID: <20030914191114.C96749@carver.gumbysoft.com> References: <31929.12.238.113.137.1063485645.squirrel@mail.yazzy.org> <20030914102130.K93499@carver.gumbysoft.com> <33165.12.238.113.137.1063565187.squirrel@mail.yazzy.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: mystery kernel spew X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 02:13:11 -0000 On Sun, 14 Sep 2003, masta wrote: > I owe you a beer Doug (or a soda-pop)! ;) hehe :) > You were correct about the sysctl.conf being the root-cause of the kernel > spew. Mike Smith ran into it one day and we spent some time debugging it. Someone made the observation that they were sysctl items and not function calls and that tipped us off. 'sysctl sysctl' is a magic incantation to dump the sysctl tree. There's a couple of other magic words. > #security.bsd.see_other_uids=0 > sysctl net.inet.tcp.blackhole=1 > sysctl net.inet.udp.blackhole=1 Heh, you even had an example :) Incidentally, if you are getting wrapping even without this, you can use a serial console to capture the output. I've had to do this for doing nasty ACPI debugging with lots of the options enabled. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org