[Gilbert Ramirez <gram@xxxxxxxxxxxxxxx>]

On Fri, 2003-09-12 at 13:44, Guy Harris wrote:
> 
> On Sep 12, 2003, at 6:11 AM, Joerg Mayer wrote:
> 
> > On Fri, Sep 12, 2003 at 08:43:27AM -0400, Neil Horman wrote:
> >> Iassumed since I didn't hear back from you that
> >> SIGINT was the most appropriate signal to use here (as opposed to
> >> SIGUSR2).
> >
> > Maybe SIGSTOP is better - I sometimes like to kill programs
> > from the command line.
> 
> SIGSTOP is generally reserved for "suspend this program", not "kill 
> this program".  Furthermore, according to the POSIX spec (and the BSD 
> and Linux man pages, at least), you can't catch or ignore it.
> 
> If by "from the command line" you mean "with a 'kill' command", you can 
> send SIGINT with a "kill" command - "kill -INT" or, on older systems, 
> "kill -2".  You can also send it with your interrupt character if 
> you've run Ethereal from a terminal window.
> 

We already stop the child capture process with SIGUSR1... why not have
the parent ethereal process catch SIGUSR1, too ?

--gilbert