TCP info spamming the logs and dmesg

[Andre Oppermann]

Mike Jakubik wrote:
> Eygene Ryabinkin wrote:
>> Andre, good day.
>>
>> Thu, Aug 16, 2007 at 08:34:05PM +0400, Eygene Ryabinkin wrote:
>>  
>>> Thu, Aug 16, 2007 at 11:14:08AM -0400, Mike Jakubik wrote:
>>>    
>>>> Is there any way to disable these, or have them log to a separate log?
>>>>       
>>
>> I had seen about four such questions for the last two weeks, so maybe
>> it is time to patch tcp(4) manpage?  The following is the very rough
>> patch for it:
>> --- tcp.4.orig    2007-08-16 20:35:06.000000000 +0400
>> +++ tcp.4    2007-08-16 20:37:33.000000000 +0400
>> @@ -259,6 +259,11 @@
>>  Maximum
>>  .Tn TCP
>>  receive window.
>> +.It Va log_debug
>> +Enable (1) or disable (0)
>> +.Tn TCP
>> +stack debugging messages.
>> +Default is 1, i.e., the logging is enabled.
>>  .It Va log_in_vain
>>  Log any connection attempts to ports where there is not a socket
>>  accepting connections.
>>   
> 
> 
> That sounds like a good idea, perhaps it would also be a good idea to 
> set the default to 0?

Yes, that is planned for the release together with all the
other performance affecting debugging features in the kernel
(WITNESS, INVARIANTS, etc).

I have updates to the tcp.4 and syncache.4 manpage in the wings
to document all changes and new sysctls.

-- 
Andre