USBPCapCmd details #135
Description
Almost certainly not a defect, but I didn't see anywhere else to ask the question.
If I'm starting a capture from the command line using usbpcapcmd directly ("USBpcapcmd -d \.\usbpcap2 -A --inject-descriptors -o c:\blah\fred.pcap") is it like ETW captures with LogMan where it'll run until it's explicitly turned off? Or is there an implicit point at which it stops?
And if you have to explicitly stop the capture, what's the way to do that via the cmd line? Just killing USBPcapCmd executables via task manager doesn't seem the right way to do it, but I don't see any command line options to stop a capture once it's started?