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=FREEMAIL_FROM,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 62FFF44C216 for ; Tue, 26 Nov 2013 13:31:34 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id E01C526306C; Tue, 26 Nov 2013 13:31:33 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org Received: from mail-yh0-f45.google.com (mail-yh0-f45.google.com [209.85.213.45]) by rubyforge.org (Postfix) with ESMTP id BD23C26305B for ; Tue, 26 Nov 2013 13:30:54 +0000 (UTC) Received: by mail-yh0-f45.google.com with SMTP id v1so2842059yhn.18 for ; Tue, 26 Nov 2013 05:30:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=tuKTawSQnZ0Mo3ARibWeThSz96RgetHx/kVD1On4SrE=; b=wa4aqs3ln0rXle20MuQM48yTqTiBGo2eM7SQx+m+Q5PBzdCf7+bwAWvA0EbHmFipnP Uy2sdxvV6ZuaVm3gSRZmpGcaIVmoS9o2UVolcm5srH/erU8ko2whsZN+151q7WvsGrfB 7UxqIHc1EhmWnUf3bQSR47kTNAumAHxSBcizQ0aVpt6j+vDr5ZOWgsitqcYodWZ52RA8 uzz1BnBlqj1PrMY3cM2NbIkltgrbRjv0FtYE6Mev/F9KeJNkUOmZy0dXyE6/0hRD06Po RR8rNZL4G9JB3O1iYYWvCcuRcwcKiK+6eMewbmt1sosh8xVGOngjVA6N8suwLGbaaCqB +hBA== X-Received: by 10.236.134.137 with SMTP id s9mr934522yhi.133.1385472653583; Tue, 26 Nov 2013 05:30:53 -0800 (PST) Received: from [192.168.1.5] ([179.217.1.154]) by mx.google.com with ESMTPSA id o27sm82433467yhb.19.2013.11.26.05.30.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Nov 2013 05:30:52 -0800 (PST) Message-ID: <5294A289.1020300@gmail.com> Date: Tue, 26 Nov 2013 11:30:49 -0200 From: Rodrigo Rosenfeld Rosas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: mongrel-unicorn@rubyforge.org Subject: What does it mean for the unicorn process to be bound to a terminal? 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mongrel-unicorn-bounces@rubyforge.org Errors-To: mongrel-unicorn-bounces@rubyforge.org For a long time I struggle to understand this part: http://unicorn.bogomips.org/SIGNALS.html "3. You can now send WINCH to the old master process so only the new workers serve requests. If your unicorn process is bound to an interactive terminal, you can skip this step." I asked a teammate and he didn't understand this part either, so maybe it's confusing for other people too. Would you mind to clarify what you mean by that? Also, a section with suggestions on how to properly automate a deployment with no downtime would be helpful. What I see is that most recipes, like the ones I've seen for Capistrano for example, will simply send a QUIT after USR2 to the old master without actually checking if the deploy was successful and won't use the WINCH and HUP signals to deal with health checking... Cheers, Rodrigo. _______________________________________________ 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