This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: signal issue
- From: "Dave Korn" <dk at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Fri, 30 Apr 2004 14:55:21 +0100
- Subject: RE: signal issue
> -----Original Message-----
> From: cygwin-owner On Behalf Of crenouli
> Sent: 30 April 2004 14:28
> I try to kill a process under cygwin. The main process need
> to kill one its
> child process. The child process is playing a music using :
> system("cat phrase3.wav > /dev/dsp ");
>
> The main process code is (pidChild is correst) :
> kill(SIGKILL, pidChild);
>
> I tried with SIGUSR2 (with a function associated to the
> SIGUSR2 signal) : same
> result.
>
> The opposite is working (child process sending a SIGURS1 to
> its father - the
> father receive the signal and call the matching function).
>
> Does cygwin has a problem to recieve a signal when a problem
> a process is busy
> (command system) ?
system (...) invokes a shell to execute the command you supplied as a child
process. The shell then invokes cat as a child process of its own. So what
probably happened is you killed the shell but left the cat program still
running.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/