On 2016-04-22 at 23:53:01 +0200, Vadim Kochan <vadi...@gmail.com> wrote: > Hi, > > I am thinking about to add dump of flows to stdout. It seems OK if > to use similar table format like in curses mode by default, but in case > of src peer info (2 lines per flow) the output processing by external scripts > or text processors might be too complex with considering of row > numbering. > > So here are my conclusions: > > 1) Default is OK - 1 line per flows with DST info only. > > 2) If "-s" option is specified - print 2 lines per flows like in curses mode. > > 3) Add "-o, --oneline" option to print src & dst info in 1 row, even > if it will be overflowed in next line - this is just for external text > processing.
I'd strongly prefer this way of implementing it - similar to the -c option for ifpps. IMO, there's bo reason to care about line overflows, as the main target will be script processing. > Also may be it would be useful to print empty columns with "*" or "-" > it will be more visually readable (probably in curses mode too) and also be > processed by awk. Either this (just make sure it's a character that can't appear inside a field), or separate the columns using comma or semicolon. -- 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 netsniff-ng+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
