From owner-freebsd-hackers  Sun Apr  7 17:20:52 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA13741
          for hackers-outgoing; Sun, 7 Apr 1996 17:20:52 -0700 (PDT)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA13727
          for <hackers@freefall.freebsd.org>; Sun, 7 Apr 1996 17:20:49 -0700 (PDT)
Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.5/8.7.3) with SMTP id UAA02363; Sun, 7 Apr 1996 20:17:59 -0400 (EDT)
Message-Id: <199604080017.UAA02363@whizzo.transsys.com>
X-Authentication-Warning: whizzo.transsys.com: Host localhost.transsys.com [127.0.0.1] didn't use HELO protocol
To: Poul-Henning Kamp <phk@critter.tfs.com>
cc: davidg@Root.COM, "Marc G. Fournier" <scrappy@ki.net>,
        "Jordan K. Hubbard" <jkh@time.cdrom.com>, dob@nasvr1.cb.att.com,
        hackers@freefall.freebsd.org
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: -current & "Connection attempt to..." console messages? 
In-reply-to: Your message of "Sun, 07 Apr 1996 22:44:48 -0000."
             <6550.828917088@critter.tfs.com> 
Date: Sun, 07 Apr 1996 20:17:59 -0400
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


> 
> I'm open to input on this, I just left it on as default to make sure there
> would be a discussion :-)

I think it should be defaulted to 'off' in the kernel, and then
optionally enabled AT THE END of /etc/rc* once all of the daemons have
been started up.  As it is now, much of the kernel message buffers are
filled up with these messages before syslogd gets a chance to start
up, and you loose a bunch of the autoconfig messages at boot time.

It might also be interesting to have a few tunable options to enable the
messages based on these other sysctl variable defined port ranges:

	net.inet.ip.portrange.first: 1024
	net.inet.ip.portrange.last: 5000
	net.inet.ip.portrange.hifirst: 40000
	net.inet.ip.portrange.hilast: 44999

That is, only for ports below net.inet.ip.portrange.first for "well
known" services.  Or a bit mask.. Or maybe something like the routing
protocol socket that gets sent messages, and an intelligent daemon
which implements logging policy..  Just some other ideas.

louie