From: Daniel Frederiksen <cyberdoc@cyberdoc.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Bandwidth Metering
Date: Wed, 29 Sep 2004 17:09:58 +0000 [thread overview]
Message-ID: <1096477798.13694.35.camel@hermes> (raw)
In-Reply-To: <603140b6040928154752febf20@mail.gmail.com>
Hey Patrick
I seem to have forgotten the point that you want to relate the bandwidth
usages to a user. In the perl script you posted a link for, the author
uses lsof. This sollution is ok, if the connection is still in the list,
however if you accumulate in a log from netfilter, the probability of
the connection still being active is reduced and not reliable. Is there
a specific reason why you want to map the user accounts, and are these
accounts system or actual users?. If they are just system accounts
running daemons, there are no point in mapping them.
If you still need the mapping, I will help you with the perl script, if
not we can use some of the previously sugested ideas.
Perhaps a more detailed description of the usage/problem would help
allot.
Daniel Frederiksen, Cyberdoc.dk
On Wed, 2004-09-29 at 13:14, Patrick Coleman wrote:
> I ran across one called culprit
> (http://freshmeat.net/projects/culprit.pl/), which does kinda what I
> want. However, by the looks of things it doesnt look like its going to
> be easy to maintain a database of user bandwidth usage using it. I
> might see what I can do about modifying it, but I'm shocking at perl :)
>
> Netfilter sounds like a much saner idea - how would you grab the user
> a packet belongs to when you parse the logfiles?
> Thanks,
> Patrick
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-09-29 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 22:47 [LARTC] Re: Bandwidth Metering Patrick Coleman
2004-09-29 10:49 ` Daniel Frederiksen
2004-09-29 11:14 ` Patrick Coleman
2004-09-29 17:09 ` Daniel Frederiksen [this message]
2004-09-29 22:45 ` Patrick Coleman
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=1096477798.13694.35.camel@hermes \
--to=cyberdoc@cyberdoc.dk \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.