[nSLUG] April Tech Talk
herbt at theria.ca
Wed Apr 22 20:47:22 ADT 2015
Yeah, my flags were -nil if I recall. Usually looking for something on a freeradius port. So it would zip along at a pretty good rate.
On April 22, 2015 3:46:26 PM ADT, Dop Ganger <nslug at fop.ns.ca> wrote:
>On Wed, 22 Apr 2015, Mike Spencer wrote:
>> If I pipe tcpdump through " | tee logfile", output from tcpdump gets
>> buffered up somewhere. Both the stdout and the logfile get updated
>> spurts that may break the tcpdump output in the middle of a line.
>I think you may want "tcpdump -l". Checking the man page on a local
>machine this exact scenario is actually listed, coincidentally enough:
>" -l Make stdout line buffered. Useful if you want to see the data
>capturing it. E.g.,
> tcpdump -l | tee dat
> tcpdump -l > dat & tail -f dat
> Note that on Windows,``line buffered'' means ``unbuffered'', so that
>WinDump will write each character individually if -l is specified.
> -U is similar to -l in its behavior, but it will cause output to be
>``packet-buffered'', so that the output is written to stdout at the end
>each packet rather than at the end of each line; this is buffered on
>platforms, including Windows."
>nSLUG mailing list
>nSLUG at nslug.ns.ca
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nSLUG