Date: Wed, 19 Mar 2003 13:18:28 +0100 From: Guido van Rooij <guido@gvr.org> To: Joris Vandalon <joris@vandalon.nl> Cc: Robert Garrett <rg70@sbcglobal.net>, John Angelmo <john@veidit.net>, current@freebsd.org Subject: Re: tcpdump delay? Message-ID: <20030319121828.GA87034@gvr.gvr.org> In-Reply-To: <20030319110801.GA97489@mezzanine.vandalon.nl> References: <3E784112.4000001@veidit.net> <20030319101554.GA553@sbcglobal.net> <20030319110801.GA97489@mezzanine.vandalon.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 19, 2003 at 12:08:01PM +0100, Joris Vandalon wrote: > > -l kills buffered output, i.e. waiting for a large amount of data before > > it starts writing > > -l doesnt kill bufferd output, in contrary, it makes the output bufferd. > > -l Make stdout line buffered. Useful if you want to see the data > while capturing it. E.g., > ``tcpdump -l | tee dat'' or ``tcpdump -l > > dat & tail -f dat''. Line buffered indeed. It does not make much sense to make it completely unbuffered because the output is ine oriented. Internally tcpdump uses setvbuf(). When not called the stdio mode is fully buffered which is even worse. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030319121828.GA87034>