From: "Jörg Hoffmann" <jh2000@root24.eu>
To: <linux-kernel@vger.kernel.org>
Subject: /proc/net/tcp information drop
Date: Tue, 29 Aug 2006 21:36:54 +0200 [thread overview]
Message-ID: <000201c6cba2$7c6bae10$2000a8c0@jhnotebook> (raw)
In-Reply-To: <Pine.LNX.4.61.0608292117320.5502@yvahk01.tjqt.qr>
Hello everyone (yes, i´m new at this list, just correct me if i´m wrong),
I have some trouble with /proc/net/tcp and tcp6
I´m not sure if its a feature or a bug or maybe some cleanup of the
cache...
A long time After a connection has been established the information about
the process name and the pid itself gets lost, just a - appears.
My own network-monitoring tool uses netstat to get some information about
the network-connections. But without the pid I can't see (I could over a few
more corners but ... crap) if there are more programs at the same pid or
even which program it is (maybe an undetected Trojan or just an user with
more connections then allowed...)
Here's a link to the netstat output
http://netstat.root24.eu/netstat.php?dump=1
And to my connection-statistics (the red colored hosts/ips have no special
meaning/ just shows unresolved/new connections)
http://netstat.root24.eu/connmon.php
Normal there is a Pid and prog name in every line... since the server is
online for about a month and some connections are even so long you can see
some 'holes'
Greetings
Jörg
next prev parent reply other threads:[~2006-08-29 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 12:53 Drop cache has no effect? Jan Engelhardt
2006-08-29 18:00 ` Andrew Morton
2006-08-29 19:21 ` Jan Engelhardt
2006-08-29 19:36 ` Jörg Hoffmann [this message]
2006-08-29 19:49 ` Andrew Morton
2006-08-30 1:08 ` OGAWA Hirofumi
2006-08-30 1:39 ` Andrew Morton
2006-08-30 5:54 ` Jan Engelhardt
2006-08-30 16:31 ` OGAWA Hirofumi
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='000201c6cba2$7c6bae10$2000a8c0@jhnotebook' \
--to=jh2000@root24.eu \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome