From: Eric Dumazet <dada1@cosmosbay.com>
To: netdev@oss.sgi.com
Subject: Not all tcp sockets are found by ss command (iproute2)
Date: Thu, 07 Oct 2004 09:53:48 +0200 [thread overview]
Message-ID: <4164F60C.6080807@cosmosbay.com> (raw)
Hi all
I sent this message 2 days ago on linux-net@vger but got no answer yet.
Maybe this list is a better place ?
I have two oddities with ss command (from iproute2 package)
linux kernel 2.6.8.1, SMP on x86_64
ss -V
ss utility, iproute2-ss040823
1) It seems TCP sockets in SYN-RECV are not displayed at all.
ss state syn-recv
Recv-Q Send-Q Local Address:Port
Peer Address:Port
<nothing>
2) It seems not all tcp sockets are fetched/displayed on a very loaded
server.
# ss -an|wc -l ; cat /proc/net/sockstat
565859
sockets: used 611269
TCP: inuse 613140 orphan 2572 tw 4747 alloc 613820 mem 116376
UDP: inuse 7
RAW: inuse 0
FRAG: inuse 1 memory 544
You can see on this sample that ss -an displayed 565859 lines, but
/proc/net/sockstat correctly said that more sockets were used.
Of course, /proc/net/tcp on such machine is not an option (never
completes), so I cant list all connections for this machine. I really
*need* a working ss command.
Are they known problems ?
Thank you
next reply other threads:[~2004-10-07 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 7:53 Eric Dumazet [this message]
2004-10-07 8:19 ` Not all tcp sockets are found by ss command (iproute2) Herbert Xu
2004-10-14 21:30 ` [1/3] [TCP] Create tcpdiag_dump_sock Herbert Xu
2004-10-14 21:33 ` [2/3] [TCP] Make tcpdiag_bc_run take tcpdiag_entry Herbert Xu
2004-10-14 21:35 ` [3/3] [TCP] Dump SYN_RECV sockets in tcpdiag Herbert Xu
2004-10-20 5:11 ` David S. Miller
2004-10-20 5:09 ` [2/3] [TCP] Make tcpdiag_bc_run take tcpdiag_entry David S. Miller
2004-10-20 5:08 ` [1/3] [TCP] Create tcpdiag_dump_sock David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4164F60C.6080807@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).