On Dec 14, 2013, at 7:35 PM, Jamal Hadi Salim <jhs@xxxxxxxxxxxx> wrote: > > Tried using close - no luck. I may have observed maybe 1 out > 100 runs where a proper shutdown was sent - which maybe an > an improvement, but i could be imagining that. OK. What happens when the shutdown guard timer runs off (it should be around 180 seconds)? > If it is any help: I am using epoll via libev but i dont > think thats the problem because it works 100% on older kernels. No idea... Best regards Michael > > cheers, > jamal > > On 12/14/13 12:36, Jamal Hadi Salim wrote: >> On 12/14/13 12:23, Michael Tuexen wrote: >> >> >>> OK. This should trigger the SHUTDOWN procedure, but leave the socket >>> alive. >>> Any reason why you can't try close() instead? >> >> I cant remember the reason - but there was one in the past. I will give >> close a try. I can access the machine with problematic kernel >> in about 1 hour from now and will post. >> >> The question is: Why does this work with older kernels. >> Or even more with the same kernel if the client doesnt >> send very fast. >> >> cheers, >> jamal >> >>> Best regards >>> Michael >>>> >>>> cheers, >>>> jamal >>>> >>> >>> >>> >> > > -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
