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: AS33070 50.56.128.0/17 X-Spam-Status: No, score=1.3 required=5.0 tests=RDNS_NONE,T_DKIM_INVALID shortcircuit=no autolearn=no version=3.3.2 X-Original-To: archivist@yhbt.net Delivered-To: archivist@dcvr.yhbt.net Received: from rubyforge.org (unknown [50.56.192.79]) by dcvr.yhbt.net (Postfix) with ESMTP id 82B9C1F5B6 for ; Thu, 25 Apr 2013 08:32:17 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id DA0C62E11C; Thu, 25 Apr 2013 08:32:16 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org X-Greylist: delayed 1777 seconds by postgrey-1.31 at rubyforge; Thu, 25 Apr 2013 08:32:10 UTC Received: from mail-oa0-f47.google.com (mail-oa0-f47.google.com [209.85.219.47]) by rubyforge.org (Postfix) with ESMTP id F0F292E11B for ; Thu, 25 Apr 2013 08:32:10 +0000 (UTC) Received: by mail-oa0-f47.google.com with SMTP id n9so2551730oag.6 for ; Thu, 25 Apr 2013 01:32:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=Odar4uEWNui9UHxUDtKVcmPf45jg7r94WGYXuVL8aUg=; b=DDbtOwOeePe3MF2L6zSsEXOppRrUsPQmO62YPPvDYlXh50MchuP4NSwk+zaWjQRMCE 3KFcXCDRna0JvvzJbaHBMmdyQg7ptUuVA6S3QBFEoKaVtxUNzG+creoRqzQfuLqWMz0X 3X2aO0A7HjjudSEfm9zHUqNpS3lGLpa02tFqUkuzHQYiB5PiNPfpZ8onVYz16o1g7sMA gBdE5NWWFBqKhmTJm89wQ3QiK12rl6SIyNappI7KyZ7TzuRAYwhyjfDp97uFB06vtC51 woPYDVEW3zYHJfZVrl1g2vRWQARskbFYL5OB7lca2rfsFaY1fdFvAIZq16umIUI+lINq jDDg== MIME-Version: 1.0 X-Received: by 10.182.156.103 with SMTP id wd7mr19179078obb.33.1366876953016; Thu, 25 Apr 2013 01:02:33 -0700 (PDT) Received: by 10.76.153.230 with HTTP; Thu, 25 Apr 2013 01:02:32 -0700 (PDT) Date: Thu, 25 Apr 2013 10:02:32 +0200 X-Google-Sender-Auth: E_wlGNLUnEsLjRMftvkE7mom2eM Message-ID: Subject: Why doesn't SIGTERM quit gracefully? From: Andreas Falk To: mongrel-unicorn@rubyforge.org X-BeenThere: mongrel-unicorn@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mongrel-unicorn-bounces@rubyforge.org Errors-To: mongrel-unicorn-bounces@rubyforge.org Hi, I'm wondering why SIGINT and SIGTERM both were chosen for the quick shutdown? I agree with SIGINT but not with SIGTERM. A lot of unix tools send SIGTERM as default (kill, runit among some) and it seems to be the standard way of telling a process to quit gracefully but not among Ruby people (there are a few other ruby processes behaving the same way). I just think it's weird that the default command will exit without taking care of their current request. Also i'm not on the mailinglist so it would be great if you could cc mail@andreasfalk.se Regards, Andreas Falk _______________________________________________ Unicorn mailing list - mongrel-unicorn@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying