Re: newbie question, tshark input from stdin

[Christopher Maynard <Christopher.Maynard () gtech com>]

Jaap Keuter <jaap.keuter@...> writes:

> That's probably because -r refers to a file (which you can seek through),
while
> -i refers to a 'stream' (which you cannot seek). Now, tcpdump is single pass
> while *shark has multi pass capability *for files*. Categorizing pipes in
*shark
> as files would open up that multi pass option, which it cannot handle, while
> tcpdump would never do that so it can access a pipe as a file.

What about allowing "-r -", but just treating it exactly the same as if "-i
-" had been specified?



___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe