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@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
