Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

> At the moment there is a timeout of 4s to allow androiddump to connect to ADB. I should be fixed right now and timeout should be 10ms (aka non-blocking socket on Windows and on Linux/FreeBSD). If it is no 10ms (no ADB daemon started), then there is only a need to do truly non-blocking socket

Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

The problem is only when compiling with autotools. With cmake the bin extcap dir is clean and it doesn't affect startup time. Btw the check you added is wise and should be done anyway in case unwanted artifacts are there. The problem with extcaps is that androiddump is the only tool that

Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

On Mar 27, 2017, at 1:14 PM, Guy Harris wrote: > Currently, with that fix, I get results like > > $ time ./tshark -r /tmp/nothing.pcap > > real0m1.407s > user0m0.312s > sys 0m0.676s > > with the extcap directory in place and results like > > $ time ./tshark -r

Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

On Mar 26, 2017, at 11:30 PM, Michał Łabędzki wrote: > Could you check if any of extcap binaries generates that delay? A lot of the delay comes from extcap *non*-binaries; the code that scans the extcap directory tried running *everything* it finds there,

Re: [Wireshark-dev] Why does the extcap stuff take so long to start up?

Hello Guy, Could you check if any of extcap binaries generates that delay? (check one by one) On "my" Ubuntu 12.04: my_extcap[4] = {androiddump, randpktdump, udpdump, my custom extcap}; $ time ./run/tshark -D # returns 21 interfaces real0m0.188s user0m0.115s sys 0m0.061s