Date: Sun, 14 Sep 2003 19:13:09 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: masta <masta@wifibsd.org> Cc: current@freebsd.org Subject: Re: mystery kernel spew Message-ID: <20030914191114.C96749@carver.gumbysoft.com> In-Reply-To: <33165.12.238.113.137.1063565187.squirrel@mail.yazzy.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030914191114.C96749>