linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Souza <thehazard@gmail.com>
To: Ron Michael Khu <ronkhu@ntsp.nec.co.jp>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Which two types signal cannot be produce in user program?
Date: Mon, 8 Nov 2004 02:12:42 -0200	[thread overview]
Message-ID: <e1e1d5f40411072012714c0b05@mail.gmail.com> (raw)
In-Reply-To: <418EEE0F.9020400@hq.ntsp.nec.co.jp>

well... I dont know if I got your question but... i believe that a
signal like SIGCHLD cant be sent to another process via normal kill(),
cuz the OS is responsible for deliver it...

  reply	other threads:[~2004-11-08  4:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08  2:38 Which two types signal cannot be produce in user program? zhc
     [not found] ` <418EEDC9.7070406@hq.ntsp.nec.co.jp>
2004-11-08  3:54   ` Ron Michael Khu
2004-11-08  4:12     ` Daniel Souza [this message]
2004-11-08  7:16       ` Glynn Clements

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=e1e1d5f40411072012714c0b05@mail.gmail.com \
    --to=thehazard@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=ronkhu@ntsp.nec.co.jp \
    /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 NNTP newsgroup(s).