Wireshark-bugs: [Wireshark-bugs] [Bug 1759] Trafic from NamedPipes can not be stoped.
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 22 Aug 2007 15:10:10 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1759


luis.ontanon@xxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Critical                    |Normal
           Priority|High                        |Medium




------- Comment #1 from luis.ontanon@xxxxxxxxx  2007-08-22 15:10 GMT -------
There's no feasible way to communicate with the process that is piping its
output to Wireshark.

There's no unequivocal means to signal a program (we do not know anything
about) to suspend or to resume (especially on windows where there's no
SIGPIPE).

On unix closing the input would have SIGPIPE being sent to the writer and it
should stop, I see no feasable way even in programmer-friendly unix to tell the
writer on the oher side of a pipe I am reading to restart.

The only way would be having a program to mimic the dumpcap-wireshark protocol
and being it to receive and handle the restart and stop.

I think the non-solution that can fix this would be to disable the stop and
restart buttons while reading from a pipe.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.