Date: Sun, 07 Apr 1996 20:17:59 -0400 From: "Louis A. Mamakos" <louie@TransSys.COM> 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 Subject: Re: -current & "Connection attempt to..." console messages? Message-ID: <199604080017.UAA02363@whizzo.transsys.com> In-Reply-To: Your message of "Sun, 07 Apr 1996 22:44:48 -0000." <6550.828917088@critter.tfs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604080017.UAA02363>