All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Johan Kullstam <kullstj-ml@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unkillable process
Date: Thu, 14 Oct 2004 17:12:54 +0200	[thread overview]
Message-ID: <81b0412b0410140812251110bb@mail.gmail.com> (raw)
In-Reply-To: <87r7o1h4f3.fsf@sophia.axel.nom>

On 14 Oct 2004 08:26:08 -0400, Johan Kullstam <kullstj-ml@comcast.net> wrote:
> Albert Cahalan <albert@users.sf.net> writes:
> 
> > It's really bad when a task group leader exits.
> > The process becomes unkillable.
> 
> I have been having zombie problems since 2.6.9-rc1.  I run a boinc
> climateprediction program (related to seti@home) which leaves defunct
> "cp" processes about.  Killing the climatepredictor (called
> hadsm3um_4.03_i686-pc-linux-gnu) which spawns them causes these zombie
> cp things to get reaped.

I believe this is not related. Just a bug in the program missing
SIGCHLD and not calling waitpid.

      reply	other threads:[~2004-10-14 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14  5:20 unkillable process Albert Cahalan
2004-10-14  7:40 ` Andrew Morton
2004-10-14 12:26 ` Johan Kullstam
2004-10-14 15:12   ` Alex Riesen [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=81b0412b0410140812251110bb@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=kullstj-ml@comcast.net \
    --cc=linux-kernel@vger.kernel.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.