Re: dccp bugs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dnia Monday 24 of March 2008, Gerrit Renker napisał:
> | > | > Can you try the `ss' command from the iproute package when the
> | > | > problem occurs, using `ss -nadep' to display the DCCP states?
> | > |
> | > | $ ss -nadep
> | > | State       Recv-Q Send-Q                        Local Address:Port
> | > | Peer Address:Port
> | > | FIN-WAIT-1  0      0                                 127.0.0.1:2008
> | > | 127.0.0.1:29792  ino:0 sk:d301d3c0
>
> <snip>
>
> This is a good point, but now it gets confusing. The FIN-WAIT-1/active
> CLOSEREQ state can only happen on the server, so maybe the above output
> is not the right one.
I checked it once again and it looks almost the same. But even if the server 
is dead its socket is not that dead. At least it cannot be reused by other 
instance of server.
-- 
Regards,
Tomasz Grobelny
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [IETF DCCP]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux