From owner-freebsd-current@FreeBSD.ORG Sun Sep 14 11:47: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 34D1516A4BF for ; Sun, 14 Sep 2003 11:47:10 -0700 (PDT) Received: from mail.yazzy.org (yazzy.org [217.8.140.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23C4843F93 for ; Sun, 14 Sep 2003 11:47:08 -0700 (PDT) (envelope-from masta@wifibsd.org) Received: from localhost (localhost [127.0.0.1]) by mail.yazzy.org (Postfix) with ESMTP id C7DE13980F; Sun, 14 Sep 2003 20:47:01 +0200 (CEST) Received: from mail.yazzy.org ([127.0.0.1]) by localhost (urukhai.yazzy.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02938-03; Sun, 14 Sep 2003 20:46:30 +0200 (CEST) Received: from wifibsd.org (localhost [127.0.0.1]) by mail.yazzy.org (Postfix) with SMTP id 76E0739812; Sun, 14 Sep 2003 20:46:27 +0200 (CEST) Received: from 12-238-113-137.client.attbi.com ([12.238.113.137]) (SquirrelMail authenticated user masta@wifibsd.org) by mail.yazzy.org with HTTP; Sun, 14 Sep 2003 13:46:27 -0500 (CDT) Message-ID: <33165.12.238.113.137.1063565187.squirrel@mail.yazzy.org> Date: Sun, 14 Sep 2003 13:46:27 -0500 (CDT) From: "masta" To: In-Reply-To: <20030914102130.K93499@carver.gumbysoft.com> References: <31929.12.238.113.137.1063485645.squirrel@mail.yazzy.org> <20030914102130.K93499@carver.gumbysoft.com> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: current@freebsd.org Subject: Re: mystery kernel spew X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: masta@wifibsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2003 18:47:10 -0000 I owe you a beer Doug (or a soda-pop)! ;) You were correct about the sysctl.conf being the root-cause of the kernel spew. My sysctl.conf is having these lines: #security.bsd.see_other_uids=0 sysctl net.inet.tcp.blackhole=1 sysctl net.inet.udp.blackhole=1 See the fau paux? I must have decided to yank/paste the example incorrectly from the BLACKHOLE(4) manual, because I also included the "sysctl" word at the begining of the two lines. To error is human, but this is utter comedy if you ask me. =) I'm now able to use dmesg again, wuhoo! Thanks! -masta Allegedly Doug Whitesaid > On Sat, 13 Sep 2003, masta wrote: > >> For some time now I've have an issue with a dell laptop I use. It >> spews a bunch of kernel junk after init is spawned, and the spew >> causes my dmesg to become too full to actually produce a file I can >> send to the list that is meaningfull. > > I remember this :) > > This is probably because you have a syntax error in sysctl.conf. The > stuff thats printed is the sysctl tree. Its a debugging "feature", > although I've forgotten what exactly triggers it. > > sysctl.conf should be name=value pairs like this: > > kern.maxfiles=16384 > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org __ __ _ | \/ | __ _ ___| |_ __ _ | |\/| |/ _` / __| __/ _` | | | | | (_| \__ \ || (_| | |_| |_|\__,_|___/\__\__,_| masta@wifibsd.org http://wifibsd.org