netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: stf <stf_polska@o2.pl>
Cc: netdev@vger.kernel.org
Subject: Re: processes / net connections - an API
Date: Fri, 11 May 2007 08:47:49 -0400	[thread overview]
Message-ID: <1178887669.4093.35.camel@localhost> (raw)
In-Reply-To: <f21o3o$ri1$1@sea.gmane.org>

On Fri, 2007-11-05 at 14:41 +0200, stf wrote:
> Hi!
> 
> I want to write a library or application showing processes and net 
> connections. I was looking on ps and netstat to see how those programs 
> are retrieving the information. It seems that they are parsing /proc 
> entries.
> 
> Is there any other kernel API to get information about processes or net 
> connections?
> 

For processes, take a look at kernel-sources/accounting/*
For networking, your question is hard to answer because netstat really
wont tell you much about flows; in any case, but take a look at
iproute2-sources/iproute2/misc/*

cheers,
jamal



      reply	other threads:[~2007-05-11 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 12:41 processes / net connections - an API stf
2007-05-11 12:47 ` jamal [this message]

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=1178887669.4093.35.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=netdev@vger.kernel.org \
    --cc=stf_polska@o2.pl \
    /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).