Wireshark-bugs: [Wireshark-bugs] [Bug 13119] extcap: stop/restart capture yields a zombie proces
Comment # 8
on bug 13119
from Simone
actually extcap-base is quite implemented. I decided not to use
extcap-base.{c,h} directly to avoid dependencies from the WS tree. However the
functions are implemented.
I know that the extcap doesn't need to handle interrupts but if you send it a
SIGTERM then it would be recommended to handle that signal to do proper
cleanup.
-------------
I also tried to run the udpdump extcap and in this case I get new processes
created every time:
first time: 1. run the capture 2. stop the capture and get:
unexpected error from select: interrupted system call
then there's a process running
simone@devel:~/wireshark/build/run/extcap$ ps aux | grep udpdump
root 4454 0.0 0.2 109432 48712 pts/0 S+ 15:39 0:00
/usr/lib/x86_64-linux-gnu/wireshark/extcap//udpdump --capture
--extcap-interface udpdump --fifo /tmp/wireshark_extcap_20161111153912_WAE1ju
second time: 1. run the capture 2. stop the capture and get:
unexpected error from select: interrupted system call
this time there are two dangling processes...
simone@devel:~/wireshark/build/run/extcap$ ps aux | grep udpdump
root 4454 0.0 0.2 109432 48712 pts/0 S+ 15:39 0:00
/usr/lib/x86_64-linux-gnu/wireshark/extcap//udpdump --capture
--extcap-interface udpdump --fifo /tmp/wireshark_extcap_20161111153912_WAE1ju
root 4620 0.0 0.2 109432 48704 pts/0 S+ 15:40 0:00
/usr/lib/x86_64-linux-gnu/wireshark/extcap//udpdump --capture
--extcap-interface udpdump --fifo /tmp/wireshark_extcap_20161111154005_AFqqMZ
simone@devel:~/wireshark/build/run/extcap$ ps aux | grep udpdump
root 4454 0.0 0.2 109432 48712 pts/0 S+ 15:39 0:00
/usr/lib/x86_64-linux-gnu/wireshark/extcap//udpdump --capture
--extcap-interface udpdump --fifo /tmp/wireshark_extcap_20161111153912_WAE1ju
root 4620 0.0 0.2 109432 48704 pts/0 S+ 15:40 0:00
/usr/lib/x86_64-linux-gnu/wireshark/extcap//udpdump --capture
--extcap-interface udpdump --fifo /tmp/wireshark_extcap_20161111154005_AFqqMZ
regards,
You are receiving this mail because:
- You are watching all bug changes.
