On Mon, Jul 13, 2015 at 12:41:10PM +0200, Daniel Borkmann wrote:
> On 07/13/2015 12:09 PM, Vadim Kochan wrote:
> >On Mon, Jul 13, 2015 at 12:31:39PM +0300, Vadim Kochan wrote:
> ...
> >>If I understood correctly, you asked to do not use separated sysctl
> >>module unless it will not be used in other places ? But these funcs can
> >>be used statically in flowtop.c so they then can be used later while
> >>sysctl refactoring ?
>
> Yes, would be good if we introduce such library bits, to also make
> consistent use of it across the project.
>
> >OK I squashed sysctl commit with traffic counters dump commit and will
> >resend series v2.
>
> Great, thanks!
>
> Btw, I think it would also be useful to have flowtop dump/list the current
> data set to the test console (like conntrack -L), so that an admin could do
> a one time snapshot dump and do some more analysis on the data afterwards.
Yes, but in that case NFCT_Q_FLUSH should not be used.
>
> Thoughts? ;)
There are a lot of thoughts ... like:
1) Print counters in separated column and highlight flow entry
depend on odd order number.
2) Print traffic rate if possible (needs to look into timestamp
info).
3) Sort by maximum rate/traffic amount/process name.
4) Group counters by process name/pid as one entry.
5) Additional move like:
- jump over 1 page (Ctlr-U/Ctrl-D like in VIM ?).
- jump to the top (gg ?).
>
> Cheers,
> Daniel
--
You received this message because you are subscribed to the Google Groups
"netsniff-ng" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
