From: Edgar Toernig <froese@gmx.de>
To: git@vger.kernel.org
Subject: Re: [Q] what to do when waitpid() returns ECHILD under signal(SIGCHLD, SIG_IGN)?
Date: Tue, 20 Jun 2006 18:09:21 +0200 [thread overview]
Message-ID: <20060620180921.7bc1cb6c.froese@gmx.de> (raw)
In-Reply-To: <7vwtbc7ll6.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>
> Somebody I met last week in Japan reported that the socks client
> he uses to cross the firewall to connect to git:// port from his
> company environment seems to do signal(SIGCHLD, SIG_IGN) before
> spawning git.
Similar problems occasionally happen with SIGPIPE. There are apps[1]
that spawn processes with SIGPIPE set to SIG_IGN giving unexpected
results, i.e. child processes that still try to produce output
(getting EPIPE on every printf, but who checks printf errors?) even
if the pipe-reader (e.g. their parent) is long gone.
Ciao, ET.
[1] i.e. KDE had this bug - don't know if it's still there.
prev parent reply other threads:[~2006-06-20 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 23:49 [Q] what to do when waitpid() returns ECHILD under signal(SIGCHLD, SIG_IGN)? Junio C Hamano
2006-06-19 23:57 ` Linus Torvalds
2006-06-20 0:36 ` Junio C Hamano
2006-06-20 0:44 ` Linus Torvalds
2006-06-20 3:11 ` [PATCH] Restore SIGCHLD to SIG_DFL where we care about waitpid() Junio C Hamano
2006-06-20 12:59 ` Petr Baudis
2006-06-20 16:09 ` Edgar Toernig [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=20060620180921.7bc1cb6c.froese@gmx.de \
--to=froese@gmx.de \
--cc=git@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 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).