All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Pryzby <justinpryzby-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: manpages: explicit set SIGCHLD to SIG_IGN is distinct from SIG_DFL
Date: Mon, 7 Apr 2008 17:20:10 -0400	[thread overview]
Message-ID: <20080407212010.GA23866@cetus> (raw)
In-Reply-To: <cfd18e0f0804071408k6a559321xd80a792f62879d81-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Mon, Apr 07, 2008 at 11:08:02PM +0200, Michael Kerrisk wrote:
> On Mon, Apr 7, 2008 at 11:04 PM, Michael Kerrisk
> <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote:
> >
> > On Mon, Apr 7, 2008 at 6:16 PM, Justin Pryzby
> > <justinpryzby-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> wrote:
> > > Version: 2.79-2
> > > File: /usr/share/man/man2/wait.2.gz
> > >
> > > the SIGCHLD action to SIG_IGN inhibits the creation of zombie
> > > processes, even though kill(1) gives the "ignore" as the default
> > > disposition.

>     Note that even though the default disposition of SIGCHLD is
>     "ignore", explicitly setting the disposition to SIG_IGN results
>     in different treatement of zombie children.
> 
> Seem okay?
Yup.

Thanks,
Justin
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2008-04-07 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 16:16 manpages: explicit set SIGCHLD to SIG_IGN is distinct from SIG_DFL Justin Pryzby
2008-04-07 21:04 ` Michael Kerrisk
     [not found]   ` <cfd18e0f0804071404j630a631ev6991dfff67fc406e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-04-07 21:08     ` Michael Kerrisk
     [not found]       ` <cfd18e0f0804071408k6a559321xd80a792f62879d81-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-04-07 21:20         ` Justin Pryzby [this message]

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=20080407212010.GA23866@cetus \
    --to=justinpryzby-rn4veauk+akrv+lv9mx5uipxlwaovq5f@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.