lkml.org 
[lkml]   [1999]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: named getting stuck in tcp_close (2.2.5-ac1, 2.2.6-ac1-ank1)
    Date
    Hello!

    > ...which appears to be at the only schedule_timeout call in tcp_close():
    ...
    > So, I guess the question here is should close() be blocking on this
    > socket? Is this a bug in the kernel or in named?

    Look at named source. If it sets SO_LINGER, it is buggy.

    Older named's set SO_LINGER only making xfer after forking,
    it was crap too, but it was harmless.

    Alexey

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:51    [W:3.093 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site