>>> gharris@xxxxxxxxx 2004-10-20 04:57:02 >>>
> I'd vote for renaming capinfo to avoid a collision. If we
> can't come up with a better name than capfileinfo - which
> I don't really think is a great name, but I'm not sure what
> would be a better name - let's use that.
How about: "capstat" or "capstats"?
If the name has to change, these two names came to mind
after reviewing the current Ethereal capinfo man page
doc at:
http://www.ethereal.com/docs/man-pages/capinfo.1.html
Of course a quick google search will show that both the
capstat and capstats names have a meaning and use
elsewhere!
Now what was funny to me was that a google on "capinfo"
got me to the tcprelay's capinfo link, the tool that prompted
this rename discussion:
http://tcpreplay.sourceforge.net/capinfo.html
Is it just me or do these tools have similar functionality?
I haven't looked at the tcprelay's capinfo source nor
the reports it generates (yet) but it smells like they
both may have diverged from common source?
Even the first line under the man page description's for
both capinfo's look remarkably similar to me.
Would a (long term) better course of action be for both
packages, ethereal and tcprelay to use the same
capinfo tool?
Just some thoughts.
Best regards,
Jim Young