Messages in this thread | | | From | kuznet@ms2 ... | Subject | Re: named getting stuck in tcp_close (2.2.5-ac1, 2.2.6-ac1-ank1) | Date | Fri, 7 May 1999 21:07:43 +0400 (MSK DST) |
| |
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/
| |