Skip to contentSkip to conversation

/proc/net/tcp not updated fast enough?

DISCUSSION Henrik Christian Grove 1 participant 1 message Oct 27, 2004 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 8 lines · Herbert Xu
Quoted 5 lines · Henrik Christian Grove

I have it running on 11[1] machines and since midnight (it's 11:47 here now) I have 2397 succesfull connections, but in 31 cases (that's 1,29% of the connections - and thus not totally ignorable) I had to read through /proc/net/tcp twice to find the uid. Does that sound plausible, or more like I'm doing something wrong?

Quoted 5 lines

/proc/net/tcp in 2.4 is inherently unreliable since it doesn't use the seqfile interface. Your best bet is to use the tcp_diag interface instead. You can either do that by using the ss command from the iproute2 suite, or you can query tcp_diag directly from C through netlink.

Thank you for the quick reply. Would you (or anyone else reading this) happen to have any hints on what to do in Perl? (I know I can call ss, but maybe there's a module with a nice interface?)

.Henrik

Signature · 3 lines
"Det er fundamentalt noget humanistisk vås, at der er noget, 
 der hedder blød matematik."
   --- citat Henrik Jeppesen, dekan for det naturvidenskabelige fakultet