From: "Dave Korn" <dk@artimi.com>
To: <cygwin@cygwin.com>
Subject: RE: signal issue
Date: Fri, 30 Apr 2004 14:12:00 -0000 [thread overview]
Message-ID: <NUTMEG9g3EnIKv8r6zH00000101@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <1083331690.4092546adbbaf@www-eleves.enib.fr>
> -----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/
next prev parent reply other threads:[~2004-04-30 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 13:51 crenouli
2004-04-30 14:12 ` Dave Korn [this message]
2004-05-03 9:20 Christian Renoulin
2004-05-04 7:27 Christian Renoulin
2004-05-04 8:21 ` Brian Dessent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NUTMEG9g3EnIKv8r6zH00000101@NUTMEG.CAM.ARTIMI.COM \
--to=dk@artimi.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).