unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Zev Blut <zblut@cerego.co.jp>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: timestamping log entries
Date: Tue, 12 Oct 2010 11:20:45 +0900	[thread overview]
Message-ID: <4CB3C5FD.4000409@cerego.co.jp> (raw)
In-Reply-To: <AANLkTikta3kbVfyfPL4qwuxtJbOk4D+vznSBsA3G=cSn@mail.gmail.com>


On 10/10/2010 05:23 PM, Jimmy Soho wrote:

> When I look in the unicorn.stdout.log and/or unicorn.stderr.log files
> some lines are timestamped, some aren't. How could I get all lines
> timestamped?

I too would really like to see some sort of time stamp for the log files.

Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2010-10-12  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-10  8:23 timestamping log entries Jimmy Soho
2010-10-12  2:20 ` Zev Blut [this message]
2010-10-12  8:43   ` Eric Wong

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:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CB3C5FD.4000409@cerego.co.jp \
    --to=zblut@cerego.co.jp \
    --cc=mongrel-unicorn@rubyforge.org \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).