RE: [Lksctp-developers] 2.5.29 + 0.5.0: sockets not released?

[Perez-Gonzalez, I. <ina...@in...>]

> I am starting to thing there is a longer timeout than expected that is
> causing it. Basically I am starting the server, sending a 
> message to it,
> then it dumps it, then I cancel it to test a change, start it 
> again [port
> busy], change port, start it again. But I have seen that when 
> I unload the
> module and reload it, I can reuse them.
> 
> I was using that little sctp_darn I built myself; now I am 
> testing it w/
> sctp_darn and cannot reproduce it, so it could also be that I 
> am not doing
> something properly. I'll send you a tarball in a private 
> e-mail so I don't
> flood the list. Anyone interested, please drop me a note :)

Duh, I found a close reason: I was not closing the socket on exit; however,
this is kind of peculiar - the OS should close automagically all of the fds
when a program exists ...