unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hanche@math.ntnu.no, kbrown@cornell.edu, emacs-devel@gnu.org
Subject: Re: Zombie subprocesses
Date: Sat, 24 Nov 2012 01:45:46 -0800	[thread overview]
Message-ID: <50B0974A.7040201@cs.ucla.edu> (raw)
In-Reply-To: <83wqxbs811.fsf@gnu.org>

On 11/24/2012 12:46 AM, Eli Zaretskii wrote:
> Is leaving zombie processes here and there really worse than the
> conflict with GTK-launched subprocesses?

My impression is yes, as the zombies can exhaust process slots,
which means the user won't be able to run subprocesses.
This could happen pretty quickly on a system where the number
of processes that a single user can run is limited to a small
number, for quota or other reasons (ulimit -u).  On the system
I happened to be running on when I was typing this message,
the limit was 100 processes per user.  This is pretty low,
but it's not ridiculously low.

In contrast, the conflict with GTK-launched subprocesses means
that GTK won't report proper exit statuses and will chatter
misleading messages to the user.  This is a real bug, sometimes
fairly serious, but still, it's typically less serious than not being
able to run subprocesses at all.



  reply	other threads:[~2012-11-24  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 21:49 Zombie subprocesses Harald Hanche-Olsen
2012-11-23 22:23 ` Paul Eggert
2012-11-23 22:33   ` Ken Brown
2012-11-24  6:19     ` Eli Zaretskii
2012-11-24  8:24   ` Chong Yidong
2012-11-24  8:26   ` Paul Eggert
2012-11-24  8:46     ` Eli Zaretskii
2012-11-24  9:45       ` Paul Eggert [this message]
2012-11-24 10:10     ` Harald Hanche-Olsen
2012-11-27  2:36       ` Paul Eggert
2012-11-24  5:51 ` James Cloos

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50B0974A.7040201@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=hanche@math.ntnu.no \
    --cc=kbrown@cornell.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).