https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2879
Summary: feature request: disable stdio buffering in text2pcap
Product: Wireshark
Version: 1.0.3
Platform: All
OS/Version: All
Status: NEW
Severity: Minor
Priority: Low
Component: Extras
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: stephane_chazelas@xxxxxxxx
Build Information:
TShark 1.0.3
Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GLib 2.16.5, with libpcap 0.9.8, with libz 1.2.3.3, with POSIX
capabilities (Linux), with libpcre 7.6, without SMI, with ADNS, with Lua 5.1,
with GnuTLS 2.4.1, with Gcrypt 1.4.1, with MIT Kerberos.
Running on Linux 2.6.24.2, with libpcap version 0.9.8.
Built using gcc 4.3.2.
--
Hi, this is a feature request.
editcap uses stdio (fwrite) when writing the generated pcap file. That means
that when piping to tshark -li-, the packets are not decoded straight away but
after text2pcap stdout's stdio buffer is full.
It would be nice to have an option to turn off that buffering or better to do a
fflush(3) after each packet is output.
Example:
while :; do printf '0000 %02x\n' $(seq 100); sleep 1; done | text2pcap -qu 1,1
- - | tshark -li-
(on a GNU system)
You have to wait a few seconds to see the first packets.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
