Hi list,
For a while I'd been meaning to submit a "splitcap" tool to provide
rich command-line splitting capabilities. I'd planned on extending
Graeme Hewson's submitted splitcap util (and making it work), but just
haven't had the time.
I do, however, have an extremely simple splitcap utility available now
- it simply allows the user to split a file, either into <n> number of
slices of equal # of packets, or to split a file into (up to, optional)
<n> number of slices of size <p>. Files are created in user-specified
location (or local dir by default) in format originalfilename +
"-splitxxxx".
Usage is as follows:
Usage: splitcap [-h] [-s <# of frames>] [-n <number of slices>]
<capfile> [destination directory]
where -s <# of frames> specifies the number of frames per slice
-h produces this help listing
-n <number of slices> specifies the maximum number of slices to
create. If specified without -s, creates the specified
number of slices, of equal number of packets each. If specified
with -s, creates up to the specified number of
slices, of the specified number of packets each.
<capfile> is the name of the file to split.
[destination directory] is the location where split files will be
saved. If no directory is specified, the local directory is
assumed. Slices are saved with name "<capfile>-splitxxxx", where
xxxx is the split number.
I constantly find this extremely useful, mostly since it's magnitudes
faster than repeatedly running editcap since I only have to take one or
possibly two read passes through the file, and with very large files
this might mean the difference between an hour or days to split - and
figure others might find it the same.
Since it doesn't look like the more rich splitcap is coming anytime
soon, should I go ahead and submit this "simple" splitcap?
Ian
