IMHO capinfos, when finished processing, should exit with an error status
authorwmeier <wmeier@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 6 Apr 2011 01:41:03 +0000 (01:41 +0000)
committerwmeier <wmeier@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 6 Apr 2011 01:41:03 +0000 (01:41 +0000)
commit7771b7b5cd54a240c8a054a238cee1fc0cfbed38
tree0861666e6404b7db9245c44d10c8dc10fdf336c3
parentb3e6ed81ac8620522d1d8d140bb099dbbdc6e7cf
IMHO capinfos, when finished processing, should exit with an error status
 if an error occurred while processing.
E.G.,: For the default (no -C option):
  'capinfos invalid.xxx' or 'capinfos a.pcap invalid.xxx c.pcap'
 should exit with an error status
  (after processing all the input args) if there is an error for invalid.xxx.

With this fix, I expect fuzz-test.sh (and list_protos_in_cap.sh
and presumably other scripts) will work a bit more as as expected.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@36487 f5534014-38df-0310-8fa8-9805f1628bb7
capinfos.c
doc/capinfos.pod