From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-2.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 63C7D44C1AE; Thu, 21 Aug 2014 20:32:35 +0000 (UTC) Date: Thu, 21 Aug 2014 20:32:35 +0000 From: Eric Wong To: Jonathan del Strother Cc: unicorn-public@bogomips.org Subject: Re: Worker SIGABRT takes down all workers? Message-ID: <20140821203235.GA12050@dcvr.yhbt.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: Jonathan del Strother wrote: > So, as far as I can tell, the SIGABRT in a worker causes all siblings > workers to be reaped and restarted. Is that intended/expected? > Shouldn't it just kill the single worker & restart that? Not intended or expected. I cannot reproduce it by doing: kill -ABRT $WORKER_PID Can you? Can you setup a small test case which reproduces the issue? Is anything else running that could be sending signals to all workers? Thanks for any more info you can provide.