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=-0.2 required=5.0 tests=AWL shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: archivist@yhbt.net Delivered-To: archivist@dcvr.yhbt.net Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com [50.56.192.79]) by dcvr.yhbt.net (Postfix) with ESMTP id 262081F7A9 for ; Thu, 23 Feb 2012 05:23:23 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 5B548262FF6; Thu, 23 Feb 2012 05:23:22 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by rubyforge.org (Postfix) with ESMTP id DB59E262FF3 for ; Thu, 23 Feb 2012 05:19:54 +0000 (UTC) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 63B4C1F7A7; Thu, 23 Feb 2012 05:19:54 +0000 (UTC) Date: Thu, 23 Feb 2012 05:19:54 +0000 From: Eric Wong To: unicorn list Subject: Re: using unicorn as a local development server Message-ID: <20120223051953.GA31014@dcvr.yhbt.net> References: <20120223043007.GA20356@dcvr.yhbt.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 "Patrick J. Collins" wrote: > > You shouldn't even need the logger directive, it goes to stderr by > > default so your console will still show it. > > Hmm that's odd because I noticed as soon as I began using unicorn that I got > very little output. For example, running my app and browsing to various pages, this is all I see: > None of the development.log output is getting piped into this, so that's why I > thought doing the Logger.new(STDOUT) would get that behavior to happen just as > it does with the default rails server. Odd, not sure what Rails is doing (I don't normally use Rails). It must be something weird with the way Rails modifies all existing logger objects (I know it clobbers the default logger formatter somehow as mentioned in the FAQ). Oh well, I suppose your workaround is as good as any. _______________________________________________ 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