I would say keep it... It doesn't hurt anything, and it may actually be
useful - say if you modify the capture file outside of ethereal - for
example, if you capture it with something that ethereal can't capture
from directly. Then you don't have to go and re-open the file, just
click reload. Does reload actually re-open the file, or does it just
seek 0? If the latter, I'd say change it to actually close and re-open
the file.
-- Nathan
Gilbert Ramirez wrote:
>
> On Thu, Jan 27, 2000 at 02:27:10AM -0800, Guy Harris wrote:
> > > "File:Reload" does *not* clear the display filter, so if you have a
> > > display filter set that shows only some packets, after a "File:Reload"
> > > those will be the only packets displayed.
> >
> > Speaking of "File:Reload", given that it doesn't clear the display
> > filter (and it'd be overkill to make it do so - clearing the display
> > filter with, say, the Reset button does a good-enough job of, umm,
> > clearing the display filter; re-reading the file simply isn't necessary
> > in order to just clear the filter), and that it's no longer needed in
> > order to follow a live capture in the display, is there any reason to
> > keep it around?
>
> Not that I can think of. It can disappear, since it's reason for
> existence was for the enabling the display filter back when we used
> libpcap for display filtering, and literally had to reload the trace
> file via libpcap.
>
> --gibert
--
------------------------------------------------------------
Nathan Neulinger EMail: nneul@xxxxxxx
University of Missouri - Rolla Phone: (573) 341-4841
CIS - Systems Programming Fax: (573) 341-4216